Re: [stage1][PATCH] Make TOPN counter dynamically allocated.
On Wed, 3 Jun 2020, Martin Liška wrote: > Sorry for the breakage. Can you please paste full build output for the > problematic .o file? > > I bet it's a C file compilation, where we should use: > > __sync_val_compare_and_swap (counter, 0, (intptr_t)node); > > Can you please test it? c++ -std=c++11 -fno-PIE -c -g -DIN_GCC -fno-strict-aliasing -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wno-format -Wmissing-format-attribute -Wove rloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-st rings -fno-common -Wno-error -DHAVE_CONFIG_H -I. -I. -I/scratch/tmp/gerald/GCC-H EAD/gcc -I/scratch/tmp/gerald/GCC-HEAD/gcc/. -I/scratch/tmp/gerald/GCC-HEAD/gcc/../include -I./../intl -I/scratch/tmp/gerald/GCC-HEAD/gcc/../libcpp/include -I/home/gerald/11-i386/include -I/scratch/tmp/gerald/GCC-HEAD/gcc/../libdecnumber -I/scratch/tmp/gerald/GCC-HEAD/gcc/../libdecnumber/dpd -I../libdecnumber -I/scrat ch/tmp/gerald/GCC-HEAD/gcc/../libbacktrace -I. -I. -I/scratch/tmp/gerald/GCC-H EAD/gcc -I/scratch/tmp/gerald/GCC-HEAD/gcc/. -I/scratch/tmp/gerald/GCC-HEAD/gcc/ ../include -I./../intl -I/scratch/tmp/gerald/GCC-HEAD/gcc/../libcpp/include -I/home/gerald/11-i386/include -I/scratch/tmp/gerald/GCC-HEAD/gcc/../libdecnumber -I/scratch/tmp/gerald/GCC-HEAD/gcc/../libdecnumber/dpd -I../libdecnumber -I/scrat ch/tmp/gerald/GCC-HEAD/gcc/../libbacktrace \ -DIN_GCOV_TOOL=1 -o libgcov-merge-tool.o /scratch/tmp/gerald/GCC-HEAD/gcc/../libgcc/libgcov-merge.c Alas in tonights build (and the one with JOBS=1 I run during the day) this now did not fail any longer. On the very same system and with the same invocation of the build. No I'm wondering what might have fixed this. The git lob did not show me something obvious. > I would recommend: > > $ git show --format=fuller 871e5ada6d53d5eb495cc9f323983f347487c1b2 Ah, cool. Great to know, thank you! Gerald
Re: [stage1][PATCH] Make TOPN counter dynamically allocated.
On Tue, 2 Jun 2020, Martin Liška wrote: > Ready for master? Before that, my nightly tester on i386-unknown-freebsd11 just ran into the following: /scratch/tmp/gerald/GCC-HEAD/gcc/../libgcc/libgcov.h:396:51: error: cannot initialize a parameter of type 'gcov_type' (aka 'long long') with an rvalue of type 'nullptr_t' return !__sync_val_compare_and_swap (counter, NULL, (intptr_t)node); ^~~~ /usr/include/sys/_null.h:35:14: note: expanded from macro 'NULL' #define NULLnullptr ^~~ That seems to have come in via 871e5ada6d53d5eb495cc9f323983f347487c1b2 Author: Martin Liska Date: Fri Jan 31 13:10:14 2020 +0100 Make TOPN counter dynamically allocated. : * libgcov.h (gcov_counter_add): New. (gcov_counter_set_if_null): Likewise. (gcov_topn_add_value): New. which added the gcov_counter_set_if_null function. (The data is quite misleading and appears to be when you first committed this locally? Does git have a good way to show when something was pushed?) Gerald
Re: [IMPORTANT] ChangeLog related changes
On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote: > The libstdc++ manual is written in Docbook XML, but we commit both the > XML and generated HTML pages to Git. Sometimes a small XML file can > result in dozens of mechanical changes to the generated HTML files, > which we record in the ChangeLog as: > > * doc/html/*: Regenerated. > > With the new checks we need to name every generated file individually. > > If we add that directory to the ignored_prefixes list, we won't need > to name them. But then the doc/html/* entry will give an error, and > changes to the HTML files can be committed without any ChangeLog > entry. Should we just stop mentioning the HTML in the ChangeLog? > > We could do something like the attached patch, but it seems overkill > for this one special case. The change makes sense, but indeed it feels like a very specialized case in a general script. Thinking out of the box (and admittedly with a dose of igorance, which means I am likely missing something): Is not keeping the libstdc++/doc HTML in Git a viable option? Only creating that HTML as part of releases and maybe snapshots? Gerald
Re: [IMPORTANT] ChangeLog related changes
On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote: > The libstdc++ manual is written in Docbook XML, but we commit both the > XML and generated HTML pages to Git. Sometimes a small XML file can > result in dozens of mechanical changes to the generated HTML files, > which we record in the ChangeLog as: > > * doc/html/*: Regenerated. > > With the new checks we need to name every generated file individually. > > If we add that directory to the ignored_prefixes list, we won't need > to name them. But then the doc/html/* entry will give an error, and > changes to the HTML files can be committed without any ChangeLog > entry. Should we just stop mentioning the HTML in the ChangeLog? > > We could do something like the attached patch, but it seems overkill > for this one special case. The change makes sense, but indeed it feels like a very specialized case in a general script. Thinking out of the box (and admittedly with a dose of igorance, which means I am likely missing something): Is not keeping the libstdc++/doc HTML in Git a viable option? Only creating that HTML as part of releases and maybe snapshots? Gerald
[committed] libstdc++: Update/streamline Valgrind references
Like many sites over the last year(s) valgrind.org has now moved to https. While there, replace the second of two links in the same vicinity by a purely textual reference -- easier to maintain, and in particular also better from a user experience perspective. Gerald * doc/xml/faq.xml: Adjust Valgrind reference and remove another. * doc/html/faq.html: Regenerate. --- libstdc++-v3/doc/html/faq.html | 4 ++-- libstdc++-v3/doc/xml/faq.xml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html index 18407225d7a..967e5f5f348 100644 --- a/libstdc++-v3/doc/html/faq.html +++ b/libstdc++-v3/doc/html/faq.html @@ -700,7 +700,7 @@ of a few dozen kilobytes on startup. This pool is used to ensure it's possible to throw exceptions (such as bad_alloc) even when malloc is unable to allocate any more memory. -With some versions of http://valgrind.org/; target="_top">valgrind +With some versions of https://valgrind.org; target="_top">valgrind this pool will be shown as "still reachable" when the process exits, e.g. still reachable: 72,704 bytes in 1 blocks. This memory is not a leak, because it's still in use by libstdc++, @@ -710,7 +710,7 @@ In the past, a few people reported that the standard containers appear to leak memory when tested with memory checkers such as -http://valgrind.org/; target="_top">valgrind. +valgrind. Under some (non-default) configurations the library's allocators keep free memory in a pool for later reuse, rather than deallocating it with delete diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml index cf8684e1cea..e419d3c22a0 100644 --- a/libstdc++-v3/doc/xml/faq.xml +++ b/libstdc++-v3/doc/xml/faq.xml @@ -993,7 +993,7 @@ of a few dozen kilobytes on startup. This pool is used to ensure it's possible to throw exceptions (such as bad_alloc) even when malloc is unable to allocate any more memory. -With some versions of http://www.w3.org/1999/xlink; xlink:href="http://valgrind.org/;>valgrind +With some versions of http://www.w3.org/1999/xlink; xlink:href="https://valgrind.org;>valgrind this pool will be shown as "still reachable" when the process exits, e.g. still reachable: 72,704 bytes in 1 blocks. This memory is not a leak, because it's still in use by libstdc++, @@ -1004,7 +1004,7 @@ In the past, a few people reported that the standard containers appear to leak memory when tested with memory checkers such as -http://www.w3.org/1999/xlink; xlink:href="http://valgrind.org/;>valgrind. +valgrind. Under some (non-default) configurations the library's allocators keep free memory in a pool for later reuse, rather than deallocating it with delete -- 2.26.2
[committed] wwwdocs: Update link for ARC.
Pushed. --- htdocs/readings.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/readings.html b/htdocs/readings.html index 3d654a37..2488ca9d 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -78,7 +78,7 @@ names. arc Manufacturer: Synopsys Inc (as Synopsys DesignWare softcore) CPUs include: ARC600, ARC700 - https://www.synopsys.com/designware-ip/processor-solutions/arc-processors.html;>ARC Documentation + https://www.synopsys.com/designware-ip/processor-solutions.html;>ARC Documentation ARM -- 2.26.2
[committed] libstdc++: Switch www.cs.princeton.edu to https
My first libstdc+++ commit in the new (ChangeLog) new (Git) world order, so particularly happy for advise on any mistakes or potential improvements. (Apart from the stray change that sneaked into the .xml file in the last minute somehow :-( -- that one's resolved already.) Pushed. Gerald * doc/xml/manual/policy_data_structures_biblio.xml: Switch www.cs.princeton.edu to https. * doc/html/manual/policy_data_structures.html: Regenerate. --- libstdc++-v3/doc/html/manual/policy_data_structures.html | 2 +- libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/libstdc++-v3/doc/html/manual/policy_data_structures.html b/libstdc++-v3/doc/html/manual/policy_data_structures.html index efb3b12237b..5c3498e5b65 100644 --- a/libstdc++-v3/doc/html/manual/policy_data_structures.html +++ b/libstdc++-v3/doc/html/manual/policy_data_structures.html @@ -1037,7 +1037,7 @@ . Addison-Wesley Publishing Company . [biblio.kt99fat_heaps] wwwdocs: - http://www.cs.princeton.edu/research/techreps/TR-597-99; target="_top"> + https://www.cs.princeton.edu/research/techreps/TR-597-99; target="_top"> New Heap Data Structures . diff --git a/libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml b/libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml index 1e2845bfb5c..39bd2e70b7f 100644 --- a/libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml +++ b/libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml @@ -1,4 +1,4 @@ - +B http://docbook.org/ns/docbook; version="5.0" xml:id="pbds.biblio" xreflabel="Bibliography"> @@ -738,7 +738,7 @@ http://www.w3.org/1999/xlink; - xlink:href="http://www.cs.princeton.edu/research/techreps/TR-597-99;> + xlink:href="https://www.cs.princeton.edu/research/techreps/TR-597-99;> New Heap Data Structures -- 2.26.2
[committed] wwwdocs: Remove duplicate (old) Blackfin reference.
Pushed. Gerald --- htdocs/readings.html | 1 - 1 file changed, 1 deletion(-) diff --git a/htdocs/readings.html b/htdocs/readings.html index 09420335..3d654a37 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -94,7 +94,6 @@ names. Blackfin Manufacturer: Analog Devices - https://www.analog.com/en/products/processors-dsp/dsp/blackfin.html;>Blackfin Documentation https://www.analog.com/en/products/processors-microcontrollers/processors-dsp/blackfin-embedded-processors.html;>Blackfin Documentation -- 2.26.2
[committed] wwwdocs: Update reference to Intel's pcommit deprecation.
Pushed. Gerald --- htdocs/gcc-5/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/gcc-5/changes.html b/htdocs/gcc-5/changes.html index 536ab6c0..efa322b1 100644 --- a/htdocs/gcc-5/changes.html +++ b/htdocs/gcc-5/changes.html @@ -1084,7 +1084,7 @@ are not listed here). IA-32/x86-64 Support for the https://software.intel.com/en-us/blogs/2016/09/12/deprecate-pcommit-instruction;>deprecated + href="https://software.intel.com/content/www/us/en/develop/blogs/deprecate-pcommit-instruction.html;>deprecated pcommit instruction has been removed. -- 2.26.2
[committed] wwwdocs: Simplify language in gitwrite.html.
I noticed we have a tendency of using overly long language in our process documentation. This is a first step a simplifying (and trimming). Pushed. Gerald --- htdocs/gitwrite.html | 24 ++-- 1 file changed, 10 insertions(+), 14 deletions(-) diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html index e5dccd8e..36bb1a20 100644 --- a/htdocs/gitwrite.html +++ b/htdocs/gitwrite.html @@ -39,12 +39,11 @@ is not sufficient). If you already have an account on sourceware.org / gcc.gnu.org, ask overse...@gcc.gnu.org to add access to the GCC repository. Include the name of your sponsor and CC: her. -If you do not have an account yet, use https://sourceware.org/cgi-bin/pdw/ps_form.cgi;>this form, again specifying your sponsor. -We will then provision you on -gcc.gnu.org and inform you by mail. At this point, +We will then provision you and inform you by mail. At this point, check out a tree using the instructions below and add yourself to the MAINTAINERS file. Note: Your first and last names must be exactly the same between your account on gcc.gnu.org and the @@ -61,8 +60,7 @@ access policies below. Setting up your local Git tree -Once your account has been set up, check out the GCC sources by -issuing the command: +Check out the GCC sources by issuing the command: git clone git+ssh://username@gcc.gnu.org/git/gcc.git gcc @@ -99,7 +97,7 @@ git config --global user.email "Your Email Address" If you wish to use a different name or email address for GCC commits from that in $HOME/.gitconfig, you can configure -that in an individual Git tree using a similar command +that in an individual Git tree using similar invocations without --global. @@ -241,16 +239,15 @@ automatically added to the corresponding ChangeLog files based on the git commit message. See the documentation of ChangeLog format. -Make sure to rebuild any generated files that would be affected by -the patch. Make sure to check them in along with the files explicitly -modified by the patch. +Make sure to rebuild any generated files affected by +the patch and commit them with the files explicitly modified. If the patch adds any new files, such as testcases, use git add to make Git aware of them. We recommend using "git diff HEAD" after applying a patch to a local tree. Review the output to make sure that only the -changes you wanted to check in will be checked in. Also check to see +changes you want will be checked in. Also see if the copyright dates need to be updated. Use "git commit" to check in the patch; either name @@ -317,7 +314,7 @@ other developers, you can use git push as follows: git push origin $BRANCH:devel/$BRANCH -Also, please document such branches at the +Please document such branches at the list of development branches. @@ -450,9 +447,8 @@ much the same way as C function names are used). contrib/git-fetch-vendor.sh -Vendor spaces are controlled by the named vendor. Unless you are -affiliated with that vendor, do not push changes to that space without -their express permission. +Vendor spaces are controlled by the named vendor. Do not push +changes to that space without their express permission. This script will set up a new 'remote' that can be used to access the area used by a named vendor. You need to -- 2.26.2
[committed] wwwdocs: Update examples for branches and tags to newer ones.
Pushed. --- htdocs/git.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/htdocs/git.html b/htdocs/git.html index bec93ead..8c28bc02 100644 --- a/htdocs/git.html +++ b/htdocs/git.html @@ -146,12 +146,12 @@ series, Y is always nonzero and Z is always zero for a release, with other version numbers being used for development versions.) -The following list provides some representative examples: +The following are some representative examples: + releases/gcc-10 (a branch) releases/gcc-9 (a branch) - releases/gcc-8 (a branch) - releases/gcc-7.5.0 (a tag) + releases/gcc-9.3.0 (a tag) releases/gcc-4.9 (a branch) releases/gcc-4.9.0 (a tag) -- 2.26.2
Re: [PATCH v2] Fix use of singleton in optinfo framework
Okay to backport c00568f376078129196740d83946d54dc5437401 to the GCC 9
branch, Jakub?
Thanks,
Gerald
On Tue, 7 Apr 2020, Gustavo Romero via Gcc-patches wrote:
> Currently an use of get() method of dump_context singleton in optinfo
> framework causes a new class to be instantiated and when its dtor
> is called it calls delete on uninitialized data, causing an ICE.
>
> It happens when a temporary dump_context is instantiated for the 'm_saved'
> initialization in temp_dump_context::temp_dump_context. In that case it
> might happen that that temporary dump_context is not initalized properly
> and when it gets destroyed its dtor tries to delete 'm_pending', (delete an
> uninitialized optinfo *), thus calling delete on an uninitialized memory,
> or on whatever happens to be in the stack, generating an ICE.
>
> This commit fixes that issue by using singleton's static member get()
> directly to get the singleton's active instance, which doesn't instantiate
> a new class, so no dtor is called.
>
> gcc/Changelog:
> 2020-04-06 Gustavo Romero
>
> * dumpfile.c:
> (selftest::temp_dump_context::temp_dump_context): Fix ctor.
> ---
> gcc/dumpfile.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/dumpfile.c b/gcc/dumpfile.c
> index 468ffab..e392ecf 100644
> --- a/gcc/dumpfile.c
> +++ b/gcc/dumpfile.c
> @@ -2076,7 +2076,7 @@ temp_dump_context::temp_dump_context (bool
> forcibly_enable_optinfo,
> bool forcibly_enable_dumping,
> dump_flags_t test_pp_flags)
> : m_context (),
> - m_saved (_context ().get ())
> + m_saved (_context::get ())
> {
>dump_context::s_current = _context;
>if (forcibly_enable_optinfo)
>
0800-GIT-HELP: Doing a simple backport
I hope the offer by some of you to support people like me who Git appears to hate with a fervor still stands? ;-) And I volunteer to enhance our documentation if it appears useful. Usecase: I've got a patch approved and pushed to HEAD, and approved for active release branches - 13a46321516e2efd3bbb1f1899c539c6724240a9 . Now I want to backport from HEAD to the GCC 10 tree, so checked out a copy, found git cherry-pick, and gave it a try: git cherry-pick 13a46321516e2efd3bbb1f1899c539c6724240a9 Auto-merging gcc/ChangeLog CONFLICT (content): Merge conflict in gcc/ChangeLog error: could not apply 13a46321516... i386: Define __ILP32__ and _ILP32 for all 32-bit targets hint: after resolving the conflicts, mark the corrected paths hint: with 'git add ' or 'git rm ' hint: and commit the result with 'git commit' What now? I can manually fix up gcc/ChangeLog, but `git diff` then shows a fairly big diff (essentially all changes since the one I am trying to cherry pick)? So ... is git cherry-pick even the right tool? And if so, how do I best go about conflicts happening as part of that, ChangeLog or otherwise? Thanks, Gerald
[committed] Replace in the release notes by .
The validator triggered on another file that was recently edited, and searching our whole tree for similar occurrences these two are the remaining ones. The only drawback is that ids must not start with a digit, so I used ids in line with what we have in gcc-3.2/changes.html and later. (I believe I may have missed the GCC 10 instance when originally making this kind of change, and as part of the GCC 10.1 release process the GCC 11 page was then cloned.) Address thusly. Gerald --- htdocs/gcc-10/changes.html | 2 +- htdocs/gcc-11/changes.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index fc58a471..0959e4c4 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -1075,7 +1075,7 @@ typedef svbool_t pred512 __attribute__((arm_sve_vector_bits(512))); -GCC 10.1 +GCC 10.1 This is the https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVEDresolution=FIXEDtarget_milestone=10.0;>list of problem reports (PRs) from GCC's bug tracking system that are diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 235d1f86..92920476 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -144,7 +144,7 @@ a work-in-progress. - + -- 2.26.2
Re: [PATCH] i386: Define __ILP32__ and _ILP32 for all 32-bit targets
On Fri, 8 May 2020, Uros Bizjak wrote: >> A user reported that gcc -m32 on x86-64 does not define __ILP32__ >> and I found the same on i686 (with gcc -x c -dM -E /dev/null). : >> This patch does the same for all "regular" 32-bit x86 targets. >> Tested on i386-unknown-freebsd11.3 so far. > OK. Thank you, Uros. This is in mainline now. Okay to backport to the GCC 10 and ideally GCC 9 branches? (The latter is where the user report came from.) Gerald
[committed] Use instead of for the C++ ABI changes.
Having noticed this in some other case I went through all of our
pages and found this this instance in the GCC 10 release notes where
.
commit f1d2be6c9fcc52d676266e7ede123953d150aaf3
Author: Jonathan Wakely
Date: Thu May 7 11:24:04 2020 +0100
Document C++17 ABI changes in GCC 10
The old form still works in all browsers I know of, but the W3C HTML 5
checker warns about it, so better to adjust.
Pushed.
Gerald
---
htdocs/gcc-10/changes.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 2a94b13d..af40b3ad 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -411,7 +411,7 @@ int get_na??ve_pi() {
namespaces too.
-The ABI
+The ABI
of passing and returning certain C++ classes by value changed
on several targets in GCC 10, including
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94383;>AArch64,
--
2.26.2
RE: [ARM][wwwdocs]: Document Armv8.1-M, Helium Intrinsics and Cortex-M55 changes.
On Sat, 16 May 2020, Gerald Pfeifer wrote: > This brought some problems with that page which I addressed per the > follow-up patch below. Some more, notably three cases of ... => ..., note that closing . Pushed. Gerald commit bb406fa02b9a9c47861bc2246513c198bffc90bb Author: Gerald Pfeifer Date: Sat May 16 18:14:36 2020 +0200 Further markup fixes, properly closing elements. diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index ce2efe00..2a94b13d 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -805,17 +805,17 @@ typedef svbool_t pred512 __attribute__((arm_sve_vector_bits(512))); now supports this option. Support for the https://developer.arm.com/architectures/cpu-architecture/m-profile;> - Armv8.1-M Mainline Architecture has been added. + Armv8.1-M Mainline Architecture has been added. Armv8.1-M Mainline can be enabled by using the - -march=armv8.1-m.main command-line option. - + -march=armv8.1-m.main command-line option. + Support for the https://developer.arm.com/architectures/instruction-sets/simd-isas/helium/helium-intrinsics;> MVE beta ACLE intrinsics has been added. These intrinsics can be enabled by including the arm_mve.h header file and passing the - +mve or +mve.fp option extensions (for - example: -march=armv8.1-m.main+mve). + +mve or +mve.fp option extensions (for + example: -march=armv8.1-m.main+mve). Support for the Custom Datapath Extension beta ACLE https://developer.arm.com/docs/101028/0010/custom-datapath-extension;> intrinsics has been added.
RE: [ARM][wwwdocs]: Document Armv8.1-M, Helium Intrinsics and Cortex-M55 changes.
On Fri, 15 May 2020, Kyrylo Tkachov wrote: >> From: Srinath Parvathaneni >> M-profile related changes in GCC-10. > Ok. This brought some problems with that page which I addressed per the follow-up patch below. (I am not sure I would have introduced a one-element list, but kept that and just fixed markup from ... to ) Pushed. Gerald commit 93538bdb512831e9e9175b2c5c0bfb1527407b79 Author: Gerald Pfeifer Date: Sat May 16 18:06:54 2020 +0200 Fix up the latest Arm-related notes (markup, formatting,...). diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index 0d9e97f7..ce2efe00 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -807,12 +807,15 @@ typedef svbool_t pred512 __attribute__((arm_sve_vector_bits(512))); https://developer.arm.com/architectures/cpu-architecture/m-profile;> Armv8.1-M Mainline Architecture has been added. - Armv8.1-M Mainline can be enabled by using the -march=armv8.1-m.main command line option. - +Armv8.1-M Mainline can be enabled by using the + -march=armv8.1-m.main command-line option. + Support for the https://developer.arm.com/architectures/instruction-sets/simd-isas/helium/helium-intrinsics;> - MVE beta ACLE intrinsics has been added. These intrinsics can be enabled by including the arm_mve.h header file - and passing the +mve or +mve.fp option extensions (for example: -march=armv8.1-m.main+mve). + MVE beta ACLE intrinsics has been added. These intrinsics can be + enabled by including the arm_mve.h header file and passing the + +mve or +mve.fp option extensions (for + example: -march=armv8.1-m.main+mve). Support for the Custom Datapath Extension beta ACLE https://developer.arm.com/docs/101028/0010/custom-datapath-extension;> intrinsics has been added.
Re: Ping: [PATCH] wwwdocs: Add D front-end section for GCC 10 changes
On Thu, 14 May 2020, Jeff Law wrote: >> OK to commit? > OK. In fact, this seems like you shouldn't need reviews -- you're just > updating the docs for D. Agreed, though always happy to help and provide review and feedback - sometimes just a bit slow as in this case. But, indeed, you can self approve, Iain. Here is some specific feedback on the patch: + Aliases can now be created directly from any __trait that + return symbols or tuples. Previously, an AliasSeq was "returns" ? + It is now possible to detect the language ABI specified for a struct, + class, or interface using __traits(getLinkage, ...) Full stop. + Support for core.math.toPrec intrinsics have been added. "has been" + These intrinsics guarantee the rounding to specific floating-point + precisions at required points in the code. Is this about required points (by the standard) or specified (by the user/programmer)? + Optional parentheses in asm operands are now deprecated and + will be removed in a future release. Maybe omit "now" of which there's a number in the vicinity already? + Added --enable-libphobos-checking configure option to "Added a..."? + Added --with-libphobos-druntime-only configure option to Same here? + allow specifying whether to build only the core D runtime library, or + both the core and standard libraries into libphobos. This reads a bit complicated. Maybe "option to indicate whether to build..." ? Please consider those items and questions and share the patch as you'll install it - no need for review or anything. :) Thanks, Gerald
[committed] wwwdocs: Update link to IBM Journal of Research and Development.
I really don't get it why so many corporate webmasters do not put redirects in place at least for a while. Luckily we've got Google. Pushed. Gerald --- htdocs/readings.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/readings.html b/htdocs/readings.html index 086baaa1..09420335 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -610,7 +610,7 @@ names. https://en.wikipedia.org/wiki/IEEE_754r;>IEEE 754r, an ongoing revision to the IEEE 754 floating point standard. - http://researchweb.watson.ibm.com/journal/;>IBM Journal of Research and Development + https://www.research.ibm.com/journal/;>IBM Journal of Research and Development http://refspecs.linux-foundation.org/elf/elfspec_ppc.pdf;>System V PowerPC ABI -- 2.26.2
[committed] wwwdocs: Move refspecs.linuxbase.org to https.
Pushed. Gerald --- htdocs/readings.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/htdocs/readings.html b/htdocs/readings.html index 0dd27368..086baaa1 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -313,8 +313,8 @@ names. Manufacturer: IBM http://publibfp.dhe.ibm.com/epubs/pdf/dz9zr011.pdf;>z/Architecture Principles of Operation http://publibfp.dhe.ibm.com/epubs/pdf/dz9ar008.pdf;>ESA/390 Principles of Operation - http://refspecs.linuxbase.org/ELF/zSeries/lzsabi0_zSeries.html;>Linux for z Systems ABI - http://refspecs.linuxbase.org/ELF/zSeries/lzsabi0_s390.html;>Linux for S/390 ABI + https://refspecs.linuxbase.org/ELF/zSeries/lzsabi0_zSeries.html;>Linux for z Systems ABI + https://refspecs.linuxbase.org/ELF/zSeries/lzsabi0_s390.html;>Linux for S/390 ABI -- 2.26.2
[PATCH] i386: Define __ILP32__ and _ILP32 for all 32-bit targets
A user reported that gcc -m32 on x86-64 does not define __ILP32__
and I found the same on i686 (with gcc -x c -dM -E /dev/null).
The code has
if (TARGET_X32)
{
cpp_define (parse_in, "_ILP32");
cpp_define (parse_in, "__ILP32__");
}
so -mx32 does define __ILP32__.
This patch does the same for all "regular" 32-bit x86 targets.
Tested on i386-unknown-freebsd11.3 so far.
Okay?
Gerald
* config/i386/i386-c.c (ix86_target_macros): Define _ILP32 and
__ILP32__ for 32-bit targets.
---
gcc/config/i386/i386-c.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gcc/config/i386/i386-c.c b/gcc/config/i386/i386-c.c
index b46ebb289d2..891b2c68372 100644
--- a/gcc/config/i386/i386-c.c
+++ b/gcc/config/i386/i386-c.c
@@ -701,6 +701,8 @@ ix86_target_macros (void)
cpp_assert (parse_in, "cpu=i386");
cpp_assert (parse_in, "machine=i386");
builtin_define_std ("i386");
+ cpp_define (parse_in, "_ILP32");
+ cpp_define (parse_in, "__ILP32__");
}
if (!TARGET_80387)
--
2.26.2
Re: [PATCH] libgcc: aarch64: Get hwcap for FreeBSD
On Wed, 6 May 2020, Andreas Tobler wrote: > +#ifndef __FreeBSD__ >unsigned long hwcap = __getauxval (AT_HWCAP); > +#else > + unsigned long hwcap; Would it make sense to change the logic to #ifdef __FreeBSD__ .. #else .. #endif ? I believe that makes it easier to potentially extend this for other platforms in the future. Gerald
Re: wwwdocs: Add symver and -fprofile-prefix-path to changes.html
On Tue, 5 May 2020, Jan Hubicka wrote: > this patch adds mention of -fprofile-prefix-path and symver attribute. Thank you, Honza! > + href="https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/Optimize-Options.html#index-fprofile-prefix-path;>-fprofile-prefix-path > + can be used in combination with > -fprofile-generate=profile_dir and > + -fprofile-use=profile_dir to inform GCC where is the > base > + directory of built source tree in case it differs between > instrumentation > + and optimized builds. "...where the base directory ... is in case" (or "...resides in case") Maybe "instrumented" instead of "instrumentation"? And what is a "built source tree"? Can we say "build tree"? > + The symver attributes can be used to to bind symbols to "attribute" (singular) I believe? "to to" -> "to" > + specific version nodes on ELF platfroms. This is preferred to using "platforms" > + inline assembly with GAS symver directive because the > later "with the GNU as symver directive" (though "GNU as" over "GAS" is my preference, feel free to ignore). "the latter" Okay with those changes - thanks! Gerald
Re: [PATCH] wwwdocs: Document OpenMP changes in gcc-10/changes.html
On Tue, 5 May 2020, Jakub Jelinek wrote: > Ok for wwwdocs? > + Version 5.0 of the https://www.openmp.org/specifications/; > +>OpenMP specification is still only partially supported in the C > and C++ > + compilers. GCC 10 release has various newly implemented features (not > + implemented in the GCC 9 release), including What do you think of reframing this as GCC 10 adds a number of newly implemented OpenMP 5.0 features on top of the GCC 9 release such as ... , approaching full coverage of that standard. or "getting closer to"? That would position the work you have done more strongly. :-) (Are we fully covering OpenMP 5.0 with Fortran? You mention C and C++, hence the question.) Okay with a change along those lines. If you _really_ hate it, the original is okay with "The GCC 10 release adds..." or "GCC 10 adds...". Thank you, Gerald
[committed] wwwdocs: Move processors.wiki.ti.com to https.
Pushed. Gerald --- htdocs/readings.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/readings.html b/htdocs/readings.html index fde9c13d..0dd27368 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -257,7 +257,7 @@ names. pru Manufacturer: Texas Instruments - http://processors.wiki.ti.com/index.php/PRU-ICSS;>Official PRU Documentation + https://processors.wiki.ti.com/index.php/PRU-ICSS;>Official PRU Documentation https://elinux.org/Category:PRU;>Community PRU Documentation -- 2.26.2
[committed] wwwdocs: Update blackfin documentation link.
(And the winner for the longest URL is ... Analog Devices.) Pushed. Gerald --- htdocs/readings.html | 1 + 1 file changed, 1 insertion(+) diff --git a/htdocs/readings.html b/htdocs/readings.html index 2d0a4275..fde9c13d 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -95,6 +95,7 @@ names. Blackfin Manufacturer: Analog Devices https://www.analog.com/en/products/processors-dsp/dsp/blackfin.html;>Blackfin Documentation + https://www.analog.com/en/products/processors-microcontrollers/processors-dsp/blackfin-embedded-processors.html;>Blackfin Documentation c4x -- 2.26.2
[committed] wwwdocs: Convert a link to wg21.link to https.
Pushed. Gerald --- htdocs/projects/cxx-status.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html index 40cc4fd6..89e78c01 100644 --- a/htdocs/projects/cxx-status.html +++ b/htdocs/projects/cxx-status.html @@ -455,7 +455,7 @@ Coroutines https://wg21.link/p0912r5;>P0912R5 - as applied to http://wg21.link/n4861;>n4861 + as applied to https://wg21.link/n4861;>n4861 10 (requires -fcoroutines) __cpp_impl_coroutine = 201902 -- 2.26.2
RE: [PATCH] wwwdocs: Added mentioning of TX3 chip to the list of the processors
On Thu, 30 Apr 2020, Kyrylo Tkachov wrote: > Ok. Ah, and you also pushed it in Git. (I was just going to do it since Anton does not appear to have an account, and noticed it was a no-op. ;-) Thanks, Gerald
Re: [wwwdocs] Remove form for (un)subscribing from old mailing lists
On Thu, 23 Apr 2020, Jonathan Wakely wrote: > This no longer works, so direct people to the mailman listinfo pages > instead. > > OK to commit to wwwdocs? Yes, thank you! I was wondering whether we could keep something similar to this nice form, but could not come up with a good way. So a regression we'll swallow as part of the system migration. Gerald
Re: [PATCH] wwwdocs: document my changes for gcc 10
On Thu, 16 Apr 2020, David Malcolm wrote: > Validates. The wording could probably use some work. I did not really spot anything, and rather found your writing very clear. > OK to push to the website repo? Yes, thank you. > +https://cwe.mitre.org/;>CWE weakness identifiers, which Here you can omit the trailing /, verified on my end. Quite an impressive list, by the way! Gerald
Re: [PATCH] wwwdocs: Slightly improve IPA-SRA description in gcc-10/changes.html
On Tue, 14 Apr 2020, Martin Jambor wrote: > I think that the fact that IPA-SRA can now remove unused return > values deserves a special mention - and I also fixed the proposition > in the name of the pass. > > OK for wwwdocs? Yes, thank you. A small recommendation: > + The inter-procedural scalar replacement of aggregates (IPA-SRA) > pass > + was re-implemented to work at link-time and can now also remove > + calculating and passing unused return values. Here I'd use "computing" instead of "calculating". The meanings of those two words overlap, and in the sense of formal logics everything could be seen as a calculation. In the more common term x = 47*(y+1) would be more of a calculation whereas if (y > 47) x = y; else x = f(y); more of a computation. Gerald
Re: [PATCH] wwwdocs: Deprecate offloading to HSAIL
On Tue, 14 Apr 2020, Martin Jambor wrote: > for reasons described in my earlier email, I'd like to commit the > following to gcc-10/changes.html to mark offloading to HSAIL as > deprecated. > > OK? Yes, thank you. Though given what I saw/understand, you could write "...will likely be removed in GCC 11" (instead of "a future release"). Gerald
Re: [PATCH v2] Fix use of singleton in optinfo framework
On Tue, 7 Apr 2020, Gustavo Romero via Gcc-patches wrote: > gcc/Changelog: > 2020-04-06 Gustavo Romero > > * dumpfile.c: > (selftest::temp_dump_context::temp_dump_context): Fix ctor. If you approve (David, Jakub, or someone else) I can take care of committing this if you like. It would be helpful to get this resolved in the next days. Thanks, Gerald
[committed] wwwdocs: Remove extraneous space around tags.
It's generally a good idea, but now that we have been moving more towards our web pages (HTML files) being more self contained including DOCTYPE and common headers as opposed to more pre-processing upon deployment, consistency in the sources has become more important to allow for easier automated changes en large. I will continue to put focus on that going forward; this is just a small step removing extraneous space between and ; and it separates the sections of those files touch by a blank line where that's not the case yet. Pushed. Gerald --- htdocs/egcs-1.0/buildstat.html | 4 +++- htdocs/egcs-1.1/buildstat.html | 3 ++- htdocs/egcs-1.1/egcs-1.1-branch.html | 3 ++- htdocs/gcc-2.95/branch.html | 2 +- htdocs/gcc-2.95/buildstat.html | 2 +- htdocs/spam.html | 2 +- 6 files changed, 10 insertions(+), 6 deletions(-) diff --git a/htdocs/egcs-1.0/buildstat.html b/htdocs/egcs-1.0/buildstat.html index 66777148..da2a391f 100644 --- a/htdocs/egcs-1.0/buildstat.html +++ b/htdocs/egcs-1.0/buildstat.html @@ -1,10 +1,12 @@ + - Build and Test status for EGCS 1.0 +Build and Test status for EGCS 1.0 https://gcc.gnu.org/gcc.css; /> + Build and Test status for EGCS 1.0 diff --git a/htdocs/egcs-1.1/buildstat.html b/htdocs/egcs-1.1/buildstat.html index 64b4865c..6844d39c 100644 --- a/htdocs/egcs-1.1/buildstat.html +++ b/htdocs/egcs-1.1/buildstat.html @@ -1,8 +1,9 @@ + - Build and Test status for EGCS 1.1 +Build and Test status for EGCS 1.1 https://gcc.gnu.org/gcc.css; /> diff --git a/htdocs/egcs-1.1/egcs-1.1-branch.html b/htdocs/egcs-1.1/egcs-1.1-branch.html index c4cbf147..8da07327 100644 --- a/htdocs/egcs-1.1/egcs-1.1-branch.html +++ b/htdocs/egcs-1.1/egcs-1.1-branch.html @@ -1,8 +1,9 @@ + -EGCS 1.1 branch +EGCS 1.1 branch https://gcc.gnu.org/gcc.css; /> diff --git a/htdocs/gcc-2.95/branch.html b/htdocs/gcc-2.95/branch.html index 03746846..e4f20f80 100644 --- a/htdocs/gcc-2.95/branch.html +++ b/htdocs/gcc-2.95/branch.html @@ -3,7 +3,7 @@ -GCC 2.95 branch +GCC 2.95 branch https://gcc.gnu.org/gcc.css; /> diff --git a/htdocs/gcc-2.95/buildstat.html b/htdocs/gcc-2.95/buildstat.html index 1823fba6..c6029e45 100644 --- a/htdocs/gcc-2.95/buildstat.html +++ b/htdocs/gcc-2.95/buildstat.html @@ -3,7 +3,7 @@ - Build status for GCC 2.95 +Build status for GCC 2.95 https://gcc.gnu.org/gcc.css; /> diff --git a/htdocs/spam.html b/htdocs/spam.html index 2196a83b..8db948d4 100644 --- a/htdocs/spam.html +++ b/htdocs/spam.html @@ -3,7 +3,7 @@ - Dealing with SPAM +Dealing with SPAM https://gcc.gnu.org/gcc.css; /> -- 2.26.0
[committed] wwwdocs: Merge tilegx and tilepro entries, remove broken doc link.
Pushed. Walter, I could not find current doc links on mellanox.com; do you have any? Gerald --- htdocs/readings.html | 8 +--- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/htdocs/readings.html b/htdocs/readings.html index da37af6a..2d0a4275 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -292,14 +292,8 @@ names. Acronym stands for: Scalable Processor ARChitecture - tilegx + tilegx, tilepro Manufacturer: Mellanox - http://www.mellanox.com/repository/solutions/tile-scm/docs/;>Documentation - - - tilepro - Manufacturer: Mellanox - http://www.mellanox.com/repository/solutions/tile-scm/docs/;>Documentation v850 -- 2.26.0
[committed] libstdc++: Refer to Git documentation
Nice to see that our redirects work as intended. Still, preferrable to adjust URLs. Pushed. Gerald --- libstdc++-v3/ChangeLog | 6 ++ libstdc++-v3/doc/html/manual/appendix_contributing.html | 2 +- libstdc++-v3/doc/xml/manual/appendix_contributing.xml | 2 +- 3 files changed, 8 insertions(+), 2 deletions(-) diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index c358977dfbb..eb092792229 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,9 @@ +2020-04-05 Gerald Pfeifer + + * doc/xml/manual/appendix_contributing.xml: Refer to Git + documentation instead of Subversion. Switch to https. + * doc/html/manual/appendix_contributing.html: Regenerate. + 2020-04-03 Jonathan Wakely PR libstdc++/93960 diff --git a/libstdc++-v3/doc/html/manual/appendix_contributing.html b/libstdc++-v3/doc/html/manual/appendix_contributing.html index 28c46555d91..8be678eb919 100644 --- a/libstdc++-v3/doc/html/manual/appendix_contributing.html +++ b/libstdc++-v3/doc/html/manual/appendix_contributing.html @@ -68,7 +68,7 @@ mailto:ass...@gnu.org;>ass...@gnu.org, please CC the libstdc++ maintainers above so that progress can be monitored. Getting Sources - http://gcc.gnu.org/svnwrite.html; target="_top">Getting write access + https://gcc.gnu.org/gitwrite.html; target="_top">Getting write access (look for "Write after approval") Submitting Patches Every patch must have several pieces of information before it can be diff --git a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml index 79fa0ed32b8..00991128525 100644 --- a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml +++ b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml @@ -126,7 +126,7 @@ Getting Sources - http://www.w3.org/1999/xlink; xlink:href="http://gcc.gnu.org/svnwrite.html;>Getting write access + http://www.w3.org/1999/xlink; xlink:href="https://gcc.gnu.org/gitwrite.html;>Getting write access (look for "Write after approval") -- 2.26.0
Re: [committed] wwwdocs: ada: Tweak link to GNAT: The GNU Ada Compiler.
On Wed, 1 Apr 2020, Arnaud Charlet wrote: > We're investigating at Adacore whether the HTML version can be restored. Thank you. > In the mean time, pointing to > https://www.adacore.com/books/gnat-the-gnu-ada-compiler is indeed the way to > go. Done thusly (= pushed). Gerald commit 69513e9ef655783d2ae68d771ad8bd4eb878839d Author: Gerald Pfeifer Date: Sun Apr 5 23:42:41 2020 +0200 Fix up URL for the GNAT book. diff --git a/htdocs/readings.html b/htdocs/readings.html index 84fc0404..da37af6a 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -562,7 +562,7 @@ names. Other resources: https://www.adacore.com/community;>AdaCore Community Site - https://www.adacore.com/gap-static/GNAT_Book/html/;>GNAT: + https://www.adacore.com/books/gnat-the-gnu-ada-compiler;>GNAT: The GNU Ada Compiler https://www.adaic.org/resources/add_content/docs/95style/html/cover.html;>Ada Quality Style Guide
[committed] libstdc++: Move "free books" list from fsf.org to gnu.org
The fsf.org server now has a redirect to the gnu.org server; let's follow that. This is my first commit to libstdc++ using git, my first squashing (since I had a follow tweak to the ChangeLog), and my first --amend. Please advise if I can/should do something better. Thank you, Gerald * doc/xml/manual/appendix_free.xml: Move "free books" list from fsf.org to gnu.org. * doc/html/manual/appendix_free.html: Regenerate. --- libstdc++-v3/ChangeLog | 6 ++ libstdc++-v3/doc/html/manual/appendix_free.html | 2 +- libstdc++-v3/doc/xml/manual/appendix_free.xml | 2 +- 3 files changed, 8 insertions(+), 2 deletions(-) diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index beaf61b9d2b..ed2c4b77ac1 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,9 @@ +2020-04-01 Gerald Pfeifer + + * doc/xml/manual/appendix_free.xml: Move "free books" list from + fsf.org to gnu.org. + * doc/html/manual/appendix_free.html: Regenerate. + 2020-03-31 Ville Voutilainen Library-side tests for parenthesized aggregate init diff --git a/libstdc++-v3/doc/html/manual/appendix_free.html b/libstdc++-v3/doc/html/manual/appendix_free.html index b10283f78a2..9493373e9ef 100644 --- a/libstdc++-v3/doc/html/manual/appendix_free.html +++ b/libstdc++-v3/doc/html/manual/appendix_free.html @@ -116,7 +116,7 @@ manuals instead of proprietary ones. One way you can help this is to check the distribution terms of a manual before you buy it, and prefer copylefted manuals to non-copylefted ones. -[Note: We now maintain a https://www.fsf.org/licensing/doc/other-free-books.html; target="_top">web page +[Note: We now maintain a https://www.gnu.org/doc/other-free-books.html; target="_top">web page that lists free books available from other publishers]. Copyright ?? 2004, 2005, 2006, 2007 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USAVerbatim copying and distribution of this entire article are permitted worldwide, without royalty, in any medium, provided this diff --git a/libstdc++-v3/doc/xml/manual/appendix_free.xml b/libstdc++-v3/doc/xml/manual/appendix_free.xml index 7d682bbe039..dd51eae8afc 100644 --- a/libstdc++-v3/doc/xml/manual/appendix_free.xml +++ b/libstdc++-v3/doc/xml/manual/appendix_free.xml @@ -159,7 +159,7 @@ check the distribution terms of a manual before you buy it, and prefer copylefted manuals to non-copylefted ones. -[Note: We now maintain a http://www.w3.org/1999/xlink; xlink:href="https://www.fsf.org/licensing/doc/other-free-books.html;>web page +[Note: We now maintain a http://www.w3.org/1999/xlink; xlink:href="https://www.gnu.org/doc/other-free-books.html;>web page that lists free books available from other publishers]. -- 2.26.0
[committed] Move pspace.org to https.
Pushed. --- htdocs/readings.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/readings.html b/htdocs/readings.html index 40ad4d62..84fc0404 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -27,7 +27,7 @@ https://en.wikibooks.org/wiki/GNU_C_Compiler_Internals;>GNU C Compiler Internals (Wikibook), numerous contributors. - http://www.pspace.org/a/thesis/;>Compilation + https://www.pspace.org/a/thesis/;>Compilation of Functional Programming Languages using GCC -- Tail Calls by Andreas Bauer.
[committed] wwwdocs: Follow redirect for Thread Building Blocks on GitHub.
Pushed. --- htdocs/gcc-9/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/gcc-9/changes.html b/htdocs/gcc-9/changes.html index d5469ec4..74c7cde7 100644 --- a/htdocs/gcc-9/changes.html +++ b/htdocs/gcc-9/changes.html @@ -675,7 +675,7 @@ $ g++ typo.cc The C++17 implementation is no longer experimental. Parallel algorithms and execution -(requires https://github.com/intel/tbb;>Thread +(requires https://github.com/oneapi-src/oneTBB;>Thread Building Blocks 2018 or newer). memory_resource. -- 2.26.0
Re: [committed] wwwdocs: ada: Tweak link to GNAT: The GNU Ada Compiler.
On Wed, 1 Apr 2020, Gerald Pfeifer wrote: > Nice that AdaCore put in a redirect. I spoke too fast, that was a 404 page. > - https://www2.adacore.com/gap-static/GNAT_Book/html/;>GNAT: > + https://www.adacore.com/gap-static/GNAT_Book/html/;>GNAT: Arnaud, Eric, Pierre-Marie, what do you recommend? https://www.adacore.com/books/gnat-the-gnu-ada-compiler only appears to have a PDF. Is there still HTML up somewhere? (Should we remove the link - in readings.html - maybe in favor of something else?) Gerald
[committed] wwwdocs: ada: Tweak link to GNAT: The GNU Ada Compiler.
Nice that AdaCore put in a redirect. Pushed. --- htdocs/readings.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/readings.html b/htdocs/readings.html index 4101fc4b..40ad4d62 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -562,7 +562,7 @@ names. Other resources: https://www.adacore.com/community;>AdaCore Community Site - https://www2.adacore.com/gap-static/GNAT_Book/html/;>GNAT: + https://www.adacore.com/gap-static/GNAT_Book/html/;>GNAT: The GNU Ada Compiler https://www.adaic.org/resources/add_content/docs/95style/html/cover.html;>Ada Quality Style Guide -- 2.26.0
Re: [PATCH V2][wwwdocs] Document GNU-stack support added to GCC 10 for MIPS
On Mon, 30 Mar 2020, Dragan Mladjenovic wrote: > Thanks. I forgot to mention. I would need someone to commit this for me. I'll take care. Gerald
[committed] wwwdocs: Fix the link to the 2020-03-12 update on GCC 9.
Not sure where the original URL came from, but it does not work, so I looked this up in the mailing list archive and updated it. Pushed. Gerald --- htdocs/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/index.html b/htdocs/index.html index edeeb817..d14d4325 100644 --- a/htdocs/index.html +++ b/htdocs/index.html @@ -131,7 +131,7 @@ More news? Let ger...@pfeifer.com know! Status: - https://gcc.gnu.org/pipermail/gcc/2020-March/231811.html;>2020-03-12 + https://gcc.gnu.org/pipermail/gcc/2020-March/38.html;>2020-03-12 (regression fixes docs only). -- 2.25.1
[committed] wwwdocs: Switch link to libgfortran.h from ViewCVS to Git.
This is the second such case in the tree. Thanks to Frank Ch. Eigler for the updated link. Pushed. Gerald --- htdocs/gcc-4.8/changes.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/htdocs/gcc-4.8/changes.html b/htdocs/gcc-4.8/changes.html index 83f7da6c..60cf4d42 100644 --- a/htdocs/gcc-4.8/changes.html +++ b/htdocs/gcc-4.8/changes.html @@ -435,8 +435,7 @@ int i = A().f(); // error, f() requires an lvalue object (dimension(..)) has been added. Note that currently gfortran's own array descriptor is used, which is different from the one defined in TS29113, see https://gcc.gnu.org/viewcvs/trunk/libgfortran/libgfortran.h?content-type=text%2Fplainview=co;> - gfortran's header file or use the https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=libgfortran/libgfortran.h;>gfortran's header file or use the http://chasm-interop.sourceforge.net/;>Chasm Language Interoperability Tools. -- 2.25.1
[committed] wwwdocs: Switch link to check_GNU_style.sh from ViewCVS to Git.
Thanks to Frank Ch. Eigler for the updated link. Pushed. Gerald --- htdocs/contribute.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/contribute.html b/htdocs/contribute.html index 052f778e..3d03b9d1 100644 --- a/htdocs/contribute.html +++ b/htdocs/contribute.html @@ -70,7 +70,7 @@ requirements as well as requirements on code formatting. Submissions which do not conform to the standards will be returned with a request to address any such problems. To help with the preparation of patches you can use the script https://gcc.gnu.org/viewcvs/gcc/trunk/contrib/check_GNU_style.sh?view=markup;> +"https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=contrib/check_GNU_style.sh;> contrib/check_GNU_style.sh. -- 2.25.1
Re: subversion status on gcc.gnu.org
On Fri, 20 Mar 2020, Frank Ch. Eigler via Overseers wrote: > Both svn: and ssh+svn: now work for your archeological needs. > Further, URLs such as > > https://gcc.gnu.org/viewcvs?rev=279160=gcc=rev > https://gcc.gnu.org/r123456 > > are mapped to gitweb searches that try to locate the matching > From-SVN: rABCDEF commit. This way, historical URLs from bugzilla > should work. That. Is. Cool. :-) Thank you! Should we document this somewhere? (Our web pages do not appear to contain "gcc.gnu.org/r", so probably not.) On a related note, contribute.html has a link to https://gcc.gnu.org/viewcvs/gcc/trunk/contrib/check_GNU_style.sh?view=markup and gcc-4.8/changes.html has a linkto https://gcc.gnu.org/viewcvs/trunk/libgfortran/libgfortran.h?content-type=text%2Fplainview=co which are broken now. Do you have an idea how to go about those? (Happy to make those changes then.) Thanks, Gerald
[committed] wwwdocs: Slightly shorten/simplify our notes on mailing list spam.
A mail by Jonathan made me look at that page again after a looong while, and I noticed two simplifications. Pushed (though the machinery to update the web site did not appear to be working then, but I manually re-run it now). Gerald patch commit 09a7a9579b59619ea3f601b821ec8b9dd3fe708e Author: Gerald Pfeifer Date: Sun Mar 8 00:28:23 2020 +0100 Slightly shorten/simplify our notes on mailing list spam. diff --git a/htdocs/spam.html b/htdocs/spam.html index f368ad9a..2196a83b 100644 --- a/htdocs/spam.html +++ b/htdocs/spam.html @@ -15,11 +15,7 @@ wish this would not happen, it is a fact of life on an open list (we do not want to run a list where only members can post). Some simple guidelines for how to deal with SPAM to the lists can help -avoid creating unnecessary traffic on the list. - - In additional to the information provided below, you might want to check -out https://www.abuse.net;>www.abuse.net for further information -about SPAM. +avoid creating unnecessary traffic: - NEVER respond to SPAM, no matter *what* the message says about @@ -54,5 +50,8 @@ about SPAM. email address harvested this way. +In addition to the above you may want to check out +https://www.abuse.net;>www.abuse.net. +
Re: text/x-* attachments strippe
On Mon, 9 Mar 2020, Thomas König wrote: > I also seem to have missed all discussion on this change (if there was > anything). I do not understand why such a huge change was implemented > that way, and who did this. Perhaos the person(s) responsible could > speak up about this. Let's be careful - most people working on this are volunteers, and it's great that they took care and spent evenings and weekends. Could this have gone a bit smoother? Yes. More collaborative? Maybe. But it's been old system and quite an upgrade, so changes (including some inconvenient ones) are to be expected. I have found and reported and (with the little I can) helped address some issues and will continue to do so -- and am confident this is heading in the right direction. Gerald
Re: List-Id header being stripped
On Mon, 9 Mar 2020, Florian Weimer wrote: > So the difference is > > List-Id: > > vs > > List-Id: Gcc mailing list > > I guess now you need to perform a substring match. Or remove the string. Is that doable? (It does not add value, and "Gcc" is wrong spelling anyway.) Gerald
Re: Ping: [PATCH] wwwdocs: Document support for extended identifiers added to GCC 10
On Tue, 25 Feb 2020, Lewis Hyatt wrote: > Just checking whether the below is OK for gcc 10 changes.html please. Thanks! > https://gcc.gnu.org/ml/gcc-patches/2020-01/msg01667.html Yes, this looks fine to me from a web perspective. Thank you, Gerald
[committed] wwwdocs: Represent mirror admins' addresses more consistently.
Pushed. Gerald snip commit 8a562ce34e441587b87d5e5bc2ebb58f4ce630b9 Author: Gerald Pfeifer Date: Sat Mar 7 21:59:50 2020 +0100 Represent mirror admins' addresses more consistently. diff --git a/htdocs/mirrors.html b/htdocs/mirrors.html index 6813de72..462d7cd7 100644 --- a/htdocs/mirrors.html +++ b/htdocs/mirrors.html @@ -20,16 +20,16 @@ mirrors. The following sites mirror the gcc.gnu.org download site -France (no snapshots): ftp://ftp.lip6.fr/pub/gcc/;>ftp.lip6.fr, thanks to ftpmaint at lip6.fr -France, Brittany: ftp://ftp.irisa.fr/pub/mirrors/gcc.gnu.org/gcc/;>ftp.irisa.fr, thanks to ftpmaint at irisa.fr -France, Versailles: ftp://ftp.uvsq.fr/pub/gcc/;>ftp.uvsq.fr, thanks to ftpmaint at uvsq.fr -Germany, Berlin: ftp://ftp.fu-berlin.de/unix/languages/gcc/;>ftp.fu-berlin.de, thanks to ftp at fu-berlin.de -Germany: ftp://ftp.gwdg.de/pub/misc/gcc/;>ftp.gwdg.de, thanks to emoenke at gwdg.de -Germany: ftp://ftp.mpi-sb.mpg.de/pub/gnu/mirror/gcc.gnu.org/pub/gcc/;>ftp.mpi-sb.mpg.de, thanks to ftpadmin at mpi-sb.mpg.de -Germany: http://gcc.cybermirror.org;>http://gcc.cybermirror.org, thanks to Sascha Schwarz (cm at cybermirror.org) -Greece: ftp://ftp.ntua.gr/pub/gnu/gcc/;>ftp.ntua.gr, thanks to ftpadm at ntua.gr -Hungary, Budapest: http://robotlab.itk.ppke.hu/gcc/;>robotlab.itk.ppke.hu, thanks to Adam Rak (neurhlp at gmail.com) -Japan: http://ftp.tsukuba.wide.ad.jp/software/gcc/;>ftp.tsukuba.wide.ad.jp, thanks to Kohei Takahashi (tsukuba-ftp-servers at tsukuba.wide.ad.jp) +France (no snapshots): ftp://ftp.lip6.fr/pub/gcc/;>ftp.lip6.fr, thanks to ftpma...@lip6.fr +France, Brittany: ftp://ftp.irisa.fr/pub/mirrors/gcc.gnu.org/gcc/;>ftp.irisa.fr, thanks to ftpma...@irisa.fr +France, Versailles: ftp://ftp.uvsq.fr/pub/gcc/;>ftp.uvsq.fr, thanks to ftpma...@uvsq.fr +Germany, Berlin: ftp://ftp.fu-berlin.de/unix/languages/gcc/;>ftp.fu-berlin.de, thanks to f...@fu-berlin.de +Germany: ftp://ftp.gwdg.de/pub/misc/gcc/;>ftp.gwdg.de, thanks to emoe...@gwdg.de +Germany: ftp://ftp.mpi-sb.mpg.de/pub/gnu/mirror/gcc.gnu.org/pub/gcc/;>ftp.mpi-sb.mpg.de, thanks to ftpad...@mpi-sb.mpg.de +Germany: http://gcc.cybermirror.org;>http://gcc.cybermirror.org, thanks to Sascha Schwarz (c...@cybermirror.org) +Greece: ftp://ftp.ntua.gr/pub/gnu/gcc/;>ftp.ntua.gr, thanks to ftp...@ntua.gr +Hungary, Budapest: http://robotlab.itk.ppke.hu/gcc/;>robotlab.itk.ppke.hu, thanks to Adam Rak (neur...@gmail.com) +Japan: http://ftp.tsukuba.wide.ad.jp/software/gcc/;>ftp.tsukuba.wide.ad.jp, thanks to Kohei Takahashi (tsukuba-ftp-serv...@tsukuba.wide.ad.jp) Morocco: https://mirror.marwan.ma/gcc/;>mirror.marwan.ma (rsync://mirror.marwan.ma/gcc/), @@ -38,12 +38,12 @@ mirrors. The following sites mirror the gcc.gnu.org download site http://mirror.koddos.net/gcc/;>http://mirror.koddos.net/gcc/ | rsync://mirror.koddos.net/gcc/, thanks to Martin (mir...@koddos.net) at KoDDoS. -The Netherlands, Nijmegen: ftp://ftp.nluug.nl/mirror/languages/gcc;>ftp.nluug.nl, thanks to Jan Cristiaan van Winkel (jc at ATComputing.nl) -Russia, Novosibirsk: http://mirror.linux-ia64.org/gnu/gcc/;>http://mirror.linux-ia64.org/gnu/gcc/, thanks to Daniel Volchixin dan...@volchixin.co.uk -Slovakia, Bratislava: http://gcc.fyxm.net/;>gcc.fyxm.net, thanks to Jan Teluch (admin at 2600.sk) -UK: ftp://ftp.mirrorservice.org/sites/sourceware.org/pub/gcc/;>ftp://ftp.mirrorservice.org/sites/sourceware.org/pub/gcc/, thanks to mirror at mirrorservice.org +The Netherlands, Nijmegen: ftp://ftp.nluug.nl/mirror/languages/gcc;>ftp.nluug.nl, thanks to Jan Cristiaan van Winkel (j...@atcomputing.nl) +Russia, Novosibirsk: http://mirror.linux-ia64.org/gnu/gcc/;>http://mirror.linux-ia64.org/gnu/gcc/, thanks to Daniel Volchixin (dan...@volchixin.co.uk) +Slovakia, Bratislava: http://gcc.fyxm.net/;>gcc.fyxm.net, thanks to Jan Teluch (ad...@2600.sk) +UK: ftp://ftp.mirrorservice.org/sites/sourceware.org/pub/gcc/;>ftp://ftp.mirrorservice.org/sites/sourceware.org/pub/gcc/, thanks to mir...@mirrorservice.org US, San Francisco: https://bigsearcher.com/mirrors/gcc/;>https://bigsearcher.com/mirrors/gcc/, thanks to i...@bigsearcher.com -US, San Jose: http://www.netgull.com/gcc/;>http://www.netgull.com, thanks to admin at netgull.com +US, San Jose: http://www.netgull.com/gcc/;>http://www.netgull.com, thanks to ad...@netgull.com US, Michigan: http://mirrors.concertpass.com/gcc/;>http://mirrors.concertpass.com/gcc/, thanks to ad...@mirrors.concertpass.com.
Re: [PATCH] [COMMITTED] arc: Add ARC entry for gcc-10/changes.html
On Tue, 3 Mar 2020, Claudiu Zissulescu wrote: > Add ARC entry for gcc-10/changes.html What do you think of the following refinement to mark up mov and ior as code? Gerald PS: And thanks for your other feedback, Martin! diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index 710e3863..5ba388cf 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -562,9 +562,9 @@ a work-in-progress. The interrupt service routine functions save all used registers, including extension registers and auxiliary registers used by Zero Overhead Loops. - Improve code size by using multiple short instructions instead - of a single long mov or ior instruction when its long immediate - constant is known. + Improve code size by using multiple short instructions instead of + a single long mov or ior instruction when its + long immediate constant is known. Fix usage of the accumulator register for ARC600. Fix issues with uncached attribute. Remove -mq-class option.
Re: [PATCH v2] generate EH info for volatile asm statements (PR93981)
Hi J.W., On Sat, 7 Mar 2020, J.W. Jagersma wrote: >> This should wait for stage 1, IMO. Looks pretty good to me, thanks! > What does stage 1 refer to? I'm sorry, this is my first gcc patch and > I'm still learning how this all works. we have tried to cover this at https://gcc.gnu.org/develop.html . I hope this proves interesting reading (it's not too long), and if you have any questions or suggestions, let us know! Gerald
Re: gcov: reduce code quality loss by reproducible topn merging [PR92924]
On Thu, 27 Feb 2020, Gerald Pfeifer wrote:
>> This (or rather its predecessor?) breaks bootstrap on 32-bit
>> i386-unknown-freebsd11.3.
>>
>> /scratch/tmp/gerald/gcc10-devel-work/gcc-10-20200223/gcc/value-prof.c: In
>> function 'void dump_histogram_value(FILE*, histogram_value)':
>> /scratch/tmp/gerald/gcc10-devel-work/gcc-10-20200223/gcc/value-prof.c:268:28:
>> error: format '%lld' expects argument of type 'long long int', but argument
>> 3 hastype 'int' [-Werror=format=]
>> 268 |fprintf (dump_file, " all: %" PRId64 "%s, values: ",
>> |^~~
>> 269 | abs ((int64_t) hist->hvalue.counters[0]),
>> |
>> | |
>> | int
>>
>> (I'm not sure why my nightly tester has not caught this, but only
>> the snapshot did.)
> This is now https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93962 .
And Andrew had a very good hint there (thanks!).
The patch below indeed restores the build on i386-unknown-freebsd11.
Okay? Or does this qualify as obvious?
Gerald
2020-02-28 Gerald Pfeifer
Andrew Pinski
PR bootstrap/93962
* value-prof.c (dump_histogram_value): Use std::abs instead of
abs.
diff --git a/gcc/value-prof.c b/gcc/value-prof.c
index 8e9f129708a..585b909096f 100644
--- a/gcc/value-prof.c
+++ b/gcc/value-prof.c
@@ -266,7 +266,7 @@ dump_histogram_value (FILE *dump_file, histogram_value hist)
if (hist->hvalue.counters)
{
fprintf (dump_file, " all: %" PRId64 "%s, values: ",
- abs ((int64_t) hist->hvalue.counters[0]),
+ std::abs ((int64_t) hist->hvalue.counters[0]),
hist->hvalue.counters[0] < 0
? " (values missing)": "");
for (unsigned i = 0; i < GCOV_TOPN_VALUES; i++)
Re: gcov: reduce code quality loss by reproducible topn merging [PR92924]
On Mon, 24 Feb 2020, Gerald Pfeifer wrote: > This (or rather its predecessor?) breaks bootstrap on 32-bit > i386-unknown-freebsd11.3. > > /scratch/tmp/gerald/gcc10-devel-work/gcc-10-20200223/gcc/value-prof.c: In > function 'void dump_histogram_value(FILE*, histogram_value)': > /scratch/tmp/gerald/gcc10-devel-work/gcc-10-20200223/gcc/value-prof.c:268:28: > error: format '%lld' expects argument of type 'long long int', but argument 3 > hastype 'int' [-Werror=format=] > 268 |fprintf (dump_file, " all: %" PRId64 "%s, values: ", > |^~~ > 269 | abs ((int64_t) hist->hvalue.counters[0]), > | > | | > | int > > (I'm not sure why my nightly tester has not caught this, but only > the snapshot did.) This is now https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93962 . Gerald
Re: gcov: reduce code quality loss by reproducible topn merging [PR92924]
On Mon, 17 Feb 2020, Martin Liška wrote: > Patch can bootstrap on x86_64-linux-gnu and survives regression tests. This (or rather its predecessor?) breaks bootstrap on 32-bit i386-unknown-freebsd11.3. /scratch/tmp/gerald/gcc10-devel-work/gcc-10-20200223/gcc/value-prof.c: In function 'void dump_histogram_value(FILE*, histogram_value)': /scratch/tmp/gerald/gcc10-devel-work/gcc-10-20200223/gcc/value-prof.c:268:28: error: format '%lld' expects argument of type 'long long int', but argument 3 hastype 'int' [-Werror=format=] 268 |fprintf (dump_file, " all: %" PRId64 "%s, values: ", |^~~ 269 | abs ((int64_t) hist->hvalue.counters[0]), | | | | int (I'm not sure why my nightly tester has not caught this, but only the snapshot did.) Gerald
Re: [PATCH][wwwdocs] Document GNU-stack support added to GCC 10 for MIPS
On Fri, 24 Jan 2020, Dragan Mladjenovic wrote: > From: "Dragan Mladjenovic" > > diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html > index ef27c9b..7736990 100644 > --- a/htdocs/gcc-10/changes.html > +++ b/htdocs/gcc-10/changes.html > @@ -623,7 +623,14 @@ a work-in-progress. > > > > - > +MIPS > + > + The mips*-*-linux* targets now mark object files with > appropriate GNU-stack note, > +facilitating use of non-executable stack hardening on GNU/Linux. > +The soft-float targets have this feature enabled by default, while > +for hard-float targets it requires use of glibc 2.31 or later. > + > + Thanksfor preparing this! I did not see any response, but now noticed the designated MIPS maintainer Matthew Fortune (per gcc/MAINTAINERS) was not on copy. The first line is a bit long; can you please wrap? The note on hard-float targets does not seem completely clear to me: I understand it requires glibc 2.31, but per the language it still may not enabled by default even if in that case? What is the situation on the default in the hard-float case? If believe you do not have commit access, but if you share an updated patch I can apply for you. Geral
Re: [wwwdocs] Mention common attribute in gcc-10/porting_to.html
On Thu, 6 Feb 2020, Jakub Jelinek wrote: > + If tentative definitions of particular variable or variables need to be I believe that would be "a particular variable", but best to simplify to "of particular variables". > + placed in a common block, __attribute__((__common__)) can be > + used to force that behavior for those even in code compiled without > + -fcommon. Here I'd omit "for those". This makes sense to me and reads well; okay from my side. :) Gerald
[committed] wwwdocs: New GCC mirror from Rabat, Morocco
On Sun, 5 Jan 2020, Gerald Pfeifer wrote: > Happy to have you as a mirror, and if you'd like to submit a patch > for https://gcc.gnu.org/mirrors.html that'd be great. Otherwise we > can create one. I applied this patch that I created on behalf of Sami. Gerald - Log - commit c69ec31fe4eec31ec6f1c76ebec23ad69cfb85d3 Author: Gerald Pfeifer Date: Wed Feb 5 22:38:24 2020 +0100 Add mirror.marwan.ma. diff --git a/htdocs/mirrors.html b/htdocs/mirrors.html index 1917d04a..6813de72 100644 --- a/htdocs/mirrors.html +++ b/htdocs/mirrors.html @@ -30,6 +30,10 @@ mirrors. The following sites mirror the gcc.gnu.org download site Greece: ftp://ftp.ntua.gr/pub/gnu/gcc/;>ftp.ntua.gr, thanks to ftpadm at ntua.gr Hungary, Budapest: http://robotlab.itk.ppke.hu/gcc/;>robotlab.itk.ppke.hu, thanks to Adam Rak (neurhlp at gmail.com) Japan: http://ftp.tsukuba.wide.ad.jp/software/gcc/;>ftp.tsukuba.wide.ad.jp, thanks to Kohei Takahashi (tsukuba-ftp-servers at tsukuba.wide.ad.jp) +Morocco: + https://mirror.marwan.ma/gcc/;>mirror.marwan.ma + (rsync://mirror.marwan.ma/gcc/), + thanks to Sami Ait Ali Oulahcen (s...@marwan.ma) The Netherlands, Dronten: ?? http://mirror.koddos.net/gcc/;>http://mirror.koddos.net/gcc/ | ?? rsync://mirror.koddos.net/gcc/,
[committed] wwwdocs: New GCC mirror from Rabat, Morocco
On Sun, 5 Jan 2020, Gerald Pfeifer wrote: > Happy to have you as a mirror, and if you'd like to submit a patch > for https://gcc.gnu.org/mirrors.html that'd be great. Otherwise we > can create one. I applied this patch that I created on behalf of Sami. Gerald - Log - commit c69ec31fe4eec31ec6f1c76ebec23ad69cfb85d3 Author: Gerald Pfeifer Date: Wed Feb 5 22:38:24 2020 +0100 Add mirror.marwan.ma. diff --git a/htdocs/mirrors.html b/htdocs/mirrors.html index 1917d04a..6813de72 100644 --- a/htdocs/mirrors.html +++ b/htdocs/mirrors.html @@ -30,6 +30,10 @@ mirrors. The following sites mirror the gcc.gnu.org download site Greece: ftp://ftp.ntua.gr/pub/gnu/gcc/;>ftp.ntua.gr, thanks to ftpadm at ntua.gr Hungary, Budapest: http://robotlab.itk.ppke.hu/gcc/;>robotlab.itk.ppke.hu, thanks to Adam Rak (neurhlp at gmail.com) Japan: http://ftp.tsukuba.wide.ad.jp/software/gcc/;>ftp.tsukuba.wide.ad.jp, thanks to Kohei Takahashi (tsukuba-ftp-servers at tsukuba.wide.ad.jp) +Morocco: + https://mirror.marwan.ma/gcc/;>mirror.marwan.ma + (rsync://mirror.marwan.ma/gcc/), + thanks to Sami Ait Ali Oulahcen (s...@marwan.ma) The Netherlands, Dronten: ?? http://mirror.koddos.net/gcc/;>http://mirror.koddos.net/gcc/ | ?? rsync://mirror.koddos.net/gcc/,
Re: [wwwdocs] Mention powerpc*-*-*spe* deprecation in gcc-8/changes.html
On Wed, 18 Apr 2018, Jakub Jelinek wrote: > The following patch mentions the deprecation of powerpc*spe*. I know it's a little, ahem, late, but I applied this follow-up patch to avoid a link with the text "here". (More specific text is generally recommended by user design guidelines.) Gerald commit 1eed7f705ad5153ac835cf6433ce07538e400fa8 Author: Gerald Pfeifer Date: Sun Feb 2 23:48:17 2020 +0100 Make a "here" link text more specific. diff --git a/htdocs/gcc-8/changes.html b/htdocs/gcc-8/changes.html index ddc7e824..636552ab 100644 --- a/htdocs/gcc-8/changes.html +++ b/htdocs/gcc-8/changes.html @@ -42,8 +42,8 @@ You may also want to check out our Support for the powerpc*-*-*spe* target ports which have been recently unmaintained and untested in GCC has been declared -obsolete in GCC 8 as announced -https://gcc.gnu.org/ml/gcc/2018-04/msg00102.html;>here. +obsolete in GCC 8 as +https://gcc.gnu.org/ml/gcc/2018-04/msg00102.html;>announced. Unless there is activity to revive them, the next release of GCC will have their sources permanently removed.
Re: [patch, fortran, wwwdocs] PR93461 - Bogus "symbol is already defined" with long subroutine names in submodule
On Tue, 28 Jan 2020, Andrew Benson wrote: > I've attached a draft patch to update the release notes about this ABI > breakage. I don't know if I've explained it sufficiently clearly though? I do not speak Fortran, but your description was easy to read and understand for me. :-) Thank you, and okay - let's just give the Fortran team a day or two to chime in before you push the change. Gerald
[wwwdocs] Convert simulator HOWTO to git checkout instructions.
Pushed, though it would be really good for someone familiar with this
area to go through the whole document, too, for any updates.
Hans-Peter, any chance?
Gerald
---
htdocs/simtest-howto.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/simtest-howto.html b/htdocs/simtest-howto.html
index 714949d0..4bfd8b30 100644
--- a/htdocs/simtest-howto.html
+++ b/htdocs/simtest-howto.html
@@ -49,7 +49,7 @@
cd ${TOP}
-svn checkout svn://gcc.gnu.org/svn/gcc/trunk gcc
+git clone git://gcc.gnu.org/git/gcc.git gcc
# This makes sure that file timestamps are in order initially.
cd ${TOP}/gcc
contrib/gcc_update --touch
--
2.25.0
[wwwdocs] Fix markup of (to ).
A small fix on top of the last edits to gitwrite.html; spelling "<" and ">" the HTML way is painful, and visually hard to grok. Pushed. Gerald --- htdocs/gitwrite.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html index 047c139f..ad073b53 100644 --- a/htdocs/gitwrite.html +++ b/htdocs/gitwrite.html @@ -497,7 +497,7 @@ to that vendor's branches. If you have set up push access, then the branch can similarly be pushed to using: -git push vendors/vendor vendor/topic +git push vendors/vendor vendor/topic The script can be re-run with, or without --enable-push @@ -516,7 +516,7 @@ to that vendor's branches. run and starting from the most recent commit on master: -contrib/git-add-vendor-branch.sh vendor/topic master +contrib/git-add-vendor-branch.sh vendor/topic master This will create the branch both locally and on the server, but will not -- 2.25.0
[wwwdocs] Abstract away verbal references to SVN in the GOMP project description.
Technically not necessary, but while I was at it this simplified things (and there were no similarly many references anywhere else). Pushed. Gerald --- htdocs/projects/gomp/index.html | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html index 39c8d3ad..70e6d95a 100644 --- a/htdocs/projects/gomp/index.html +++ b/htdocs/projects/gomp/index.html @@ -69,7 +69,7 @@ href="https://www.openmp.org/wp-content/uploads/openmp-4.5.pdf;>OpenMP v4.5 specification has been released. October 13, 2015 -The gomp-4_1-branch has been merged into SVN +The gomp-4_1-branch has been merged into mainline, so GCC 6 and later will feature OpenMP v4.5 support for C and C++. @@ -80,10 +80,10 @@ GCC 4.9.1 release. June 18, 2014 The last major part of Fortran OpenMP v4.0 support has been -committed into SVN mainline. +committed into mainline. October 11, 2013 -The gomp-4_0-branch has been merged into SVN +The gomp-4_0-branch has been merged into mainline, so GCC 4.9 and later will feature OpenMP v4.0 support for C and C++. @@ -91,7 +91,7 @@ C and C++. The final OpenMP v4.0 specification has been released. August 2, 2011 -The gomp-3_1-branch has been merged into SVN +The gomp-3_1-branch has been merged into mainline, so GCC 4.7 and later will feature OpenMP v3.1 support. July 9, 2011 @@ -100,10 +100,10 @@ mainline, so GCC 4.7 and later will feature OpenMP v3.1 support. February 6, 2011 A draft of the OpenMP v3.1 specification has been released for public review. The gomp-3_1-branch branch has been -created in SVN and work began on implementing v3.1 support. +created and work began on implementing v3.1 support. June 6, 2008 -The gomp-3_0-branch has been merged into SVN +The gomp-3_0-branch has been merged into mainline, so GCC 4.4 and later will feature OpenMP v3.0 support. May 12, 2008 @@ -112,7 +112,7 @@ mainline, so GCC 4.4 and later will feature OpenMP v3.0 support. October 22, 2007 Draft of the OpenMP v3.0 specification has been released for public review, the gomp-3_0-branch branch has been -created in SVN and work began on implementing v3.0 support. +created and work began on implementing v3.0 support. March 9, 2006 The branch has been merged into mainline, so starting with -- 2.25.0
[wwwdocs] Abstract a statement to refer to our infrastructure, no specifics.
Another reference to svn gone - and more abstract in case of another change in 2049. Pushed. --- htdocs/contribute.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/contribute.html b/htdocs/contribute.html index 042ff069..b671354e 100644 --- a/htdocs/contribute.html +++ b/htdocs/contribute.html @@ -186,7 +186,7 @@ be plaintext rather than part of the patch since the top of the ChangeLog changes rapidly and a patch to the ChangeLog would probably no longer apply by the time your patch is reviewed. If your change fixes a PR, put text in the ChangeLog entry mentioning -the PR. The svn commit machinery understands how to +the PR. Our infrastructure understands how to extract this information and automatically append the commit log to the PR. In order to be recognized, the text must fit a particular form. It must start with "PR", and then must include the category -- 2.24.1
Re: git conversion in progress
On Wed, 22 Jan 2020, Jakub Jelinek wrote: >> The rsync.html page can be removed too, since that was a way to download >> the entire svn repo. With git clone, you get the entire repo, so rsync >> isn't needed anymore. > I disagree, it isn't just about downloading a svn repo, but mailing list > archives too: And notably our download site (for use by mirror sites): > gcc-ftp gcc ftp area () I'll take the AI to document this explicitly after my current set of outstanding changes. Gerald
Re: Add News-feed item for git transition
On Wed, 22 Jan 2020, Richard Earnshaw (lists) wrote: > We're missing a statement on the main news feed about the git transition. Lovely, thanks. Gerald PS: Lovely referring to you creating the patch, not the missing announcement. ;-)
Re: Add News-feed item for git transition
On Wed, 22 Jan 2020, Richard Earnshaw (lists) wrote: > We're missing a statement on the main news feed about the git transition. Lovely, thanks. Gerald PS: Lovely referring to you creating the patch, not the missing announcement. ;-)
Re: [wwwdocs] Add GCC10 IPA/LTO changes
On Mon, 30 Dec 2019, Jan Hubicka wrote: > here are some of changes of LTO/IPA done in GCC10. Quite a bit! :-) > +The following GCC command line options have been introduced or > improved. ...command-line... > + href="https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/Optimize-Options.html#index-fprofile-partial-training;>-fprofile-partial-training I suggest to use the mainline version of the docs unless you believe there is going to be significant changes (removals) in the future? https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html > + can now be used to inform compiler that code paths not covered by the > + train run should not be optimized for size. ...the compiler... (Is it "train run" or "training run"?) > +A large number of improvements to code generation have been made, > including > + but not limited to the following. Can you format for a smaller width here? Otherwise patches run a little wide. > +Inter-procedural scalar replacement for aggregates (IPA-SRA) pass > was re-implemented to work at link-time. The inter-procedural... > + href="https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/Optimize-Options.html#index-finline-functions;>-finline-functions > + is now enabled at -O2 and was retuned for better code size > + versus runtime performance tradeofs. Inliner heuristics was also ...trade-offs... (dash plus double f) > +Selected --param values can now be specified at > +translation unit granuality. This includes all parameters controlling > +inliner. ...the inliner > +Profile maintenance during compilation was improved and hot/cold How about "Profile maintenance during compilation and hot/cold code partitioning have been improved"? Okay with those changes. Thank you, Gerald
Re: git conversion in progress
On Mon, 13 Jan 2020, Joseph Myers wrote: > In addition, once git.html is more complete (has the list of branches > added, at least) we need to update the GCC home page to link to the new > pages in place of those for SVN, redirect the old pages to the new ones, > and generally update references to SVN in wwwdocs and the GCC manuals. I have removed all references to svnwrite.html and svn.html from our own pages, added redirects to gitwrite.html and git.html, respectively, and after svnwrite.html a few days ago now also removed svn.html. There's some further changes I have in the queue, but the web site side of things should be mostly converted now, modulo - more Git-specifics as you had pointed out, - bugs/reghunt.html which Jonathan offered to look into, and - simtest-howto.html which looks a little dead to me. Gerald
[wwwdocs] Remove svn.html which is not referenced internally any longer.
Not only have I cleaned up all internal references, there's also a redirect from svn.html to git.html in place, so users should never get a 404. Pushed. Gerald --- htdocs/svn.html | 1219 --- 1 file changed, 1219 deletions(-) delete mode 100644 htdocs/svn.html diff --git a/htdocs/svn.html b/htdocs/svn.html deleted file mode 100644 index dc60e7c8.. --- a/htdocs/svn.html +++ /dev/null @@ -1,1219 +0,0 @@ - - - - - - - -GCC: Anonymous read-only SVN access -https://gcc.gnu.org/gcc.css; /> - - - - - -GCC: Anonymous read-only SVN access - -Our SVN source repository is available read-only to the public at -large. That way you can pick up any version (including releases) of -GCC that is in our repository. - -In addition you can https://gcc.gnu.org/viewcvs/gcc/;>browse -our SVN history online. - -(Our web pages are managed via git.) - - -Using the SVN repository - -Assuming you have version 1.0.0 and higher of -http://subversion.tigris.org/;>Subversion installed, you can -check out the GCC sources using the following command: - - -svn checkout svn://gcc.gnu.org/svn/gcc/trunk SomeLocalDir - - -If you are behind a firewall that does not allow the svn protocol -through, you can replace svn:// with http://. -You may also need to modify your subversion servers file -(~/.subversion/servers) to set http-proxy-host and -http-proxy-port. You should only use the http protocol if -the svn protocol does not work; the http protocol has a higher server -overhead associated with it and will be slower. - -There is more https://gcc.gnu.org/wiki/SvnHelp;>information -about Subversion specifically for GCC in the GCC Wiki. - - - - -Generated files - -Our source tree contains a number of files that are generated -from other source files by build tools such as Bison, Autoconf, and -Gperf. Bison is now required when using SVN to access our sources, -but all other generated files are included in the source tree so that -GCC can be built without these build tools. The SVN checkout and -update operations do not insure that the timestamps of generated files -are later than those of the files they are generated from. The script -contrib/gcc_update updates the timestamps for all these -generated files. See the comments in that script for instructions on -running it. - -GCC's build system (in particular Make) uses file timestamps to -determine if a generated file needs to be updated by running a particular -build tool. Because of this, GCC's build system may believe that -a generated file needs regenerating even though its source has not -changed, and require a particular build tool to rebuild that generated -file. If the appropriate build tool is installed on your system, then -this will not be a problem. If you do not intend to make changes to -the source, you can avoid installing these build tools by running -contrib/gcc_update. - -There has been some discussion of removing these generated files -from GCC's SVN source tree (there is no discussion of removing them -from the released source tarballs). If that happens then -building GCC from the SVN source tree would require installing -the above mentioned build tools. Installing these build tools is not -particularly difficult, but can be time consuming especially if you -only occasionally install GCC on a particular system. - -The build tools that GCC uses are all available from the GNU -Project (see http://www.gnu.org;>http://www.gnu.org), -are often already available on many systems, and can often be found -already built for some systems. A partial list of these build tools -is: Autoconf, Bison, Xgettext, Automake, and Gperf. - -Conflicts when using svn update - -It is not uncommon to get svn conflict messages for some generated files -when updating your local sources from the SVN repository. Typically such -conflicts occur with autoconf generated files. - -As long as you haven't been making modifications to the generated files -or the generator files, it is safe to delete the offending file, then run -svn update again to get a new copy. - - -Branches and Tags - -A branch called branchname can be checked out with the -following command: - - -svn co svn://gcc.gnu.org/svn/gcc/branches/branchname gcc - - -(The release branch of the GCC SERIES release series -is named gcc-SERIES-branch.) - - -Similarly a tag called tagname can be checked out with the -following command: - - -svn co svn://gcc.gnu.org/svn/gcc/tags/tagname gcc - - -(The SVN tag for GCC X.Y.Z is of the form -gcc_X_Y_Z_release.) - - -The following list provides some representative examples: - - - gcc-5-branch - gcc-4_9-branch - gcc_4_9_3_release - gcc_4_9_2_release - gcc_4_9_1_release - gcc_4_9_0_release - gcc-4_8-branch - gcc-3_4-branch - - -To get a list of available branches, use the command: - - -svn ls svn://gcc.gnu.org/svn/gcc/branches - - - - - To find out the revision/date at which a branch or tag was created, use -the command svn log
[wwwdocs] Improve the presentation of our instructions on checksuming.
On the way remove a note about binary snapshots that's been commented for a while. Pushed. Gerald --- htdocs/snapshots.html | 14 -- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/htdocs/snapshots.html b/htdocs/snapshots.html index 6567a857..7776d95e 100644 --- a/htdocs/snapshots.html +++ b/htdocs/snapshots.html @@ -37,17 +37,11 @@ files so that autoconf et al aren't needed. The release script generates the file sha512.sum that provides a 512-bit checksum for the tarball and other files in the snapshot directory. Use the following command -to verify the sources: - -sha512sum --check --ignore-missing sha512.sum +to verify the sources: - + +sha512sum --check --ignore-missing sha512.sum + -- 2.24.1
[wwwdocs,Fortran] Switch over www.gnu.org to https.
Pushed. Gerald --- htdocs/fortran/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/fortran/index.html b/htdocs/fortran/index.html index b7a71de2..1d140b3a 100644 --- a/htdocs/fortran/index.html +++ b/htdocs/fortran/index.html @@ -14,7 +14,7 @@ The purpose of the GNU Fortran (GFortran) project is to develop the Fortran compiler front end and run-time libraries for GCC, the GNU Compiler Collection. GFortran development is part -of the http://www.gnu.org/;>GNU Project. We seek to bring +of the https://www.gnu.org;>GNU Project. We seek to bring free number crunching to a broad spectrum of platforms and users. In particular, the project wishes to reach users of the -- 2.24.1
[wwwdocs] Redirect svn.html to git.html.
None of our own pages refers to svn.html any longer after the updates of the last week or two; there may be some external reference, though. Pushed. Gerald --- htdocs/.htaccess | 1 + 1 file changed, 1 insertion(+) diff --git a/htdocs/.htaccess b/htdocs/.htaccess index e80d14e4..7aa9f8bb 100644 --- a/htdocs/.htaccess +++ b/htdocs/.htaccess @@ -67,6 +67,7 @@ Redirect permanent /projects.html https://gcc.gnu.org/projects/ Redirect permanent /projects/cxx1z.html https://gcc.gnu.org/projects/cxx-status.html#cxx1z Redirect permanent /projects/web.html https://gcc.gnu.org/about.html Redirect permanent /reghunt-howto.html https://gcc.gnu.org/bugs/reghunt.html +Redirect permanent /svn.html https://gcc.gnu.org/git.html Redirect permanent /svnwrite.html https://gcc.gnu.org/gitwrite.html Redirect permanent /thanks.html https://gcc.gnu.org/onlinedocs/gcc/Contributors.html Redirect permanent /timeline.html https://gcc.gnu.org/releases.html#timeline -- 2.24.1
[wwwdocs] Refer to git commands (instead of svn) in regression hunting instructions.
Jonathan spotted this, so I went ahead and addressed it (adding "git show" as another relevant command, slightly reordering the list, and removing a link to the SvnHelp wiki entry). Pushed. Gerald --- htdocs/bugs/reghunt.html | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/htdocs/bugs/reghunt.html b/htdocs/bugs/reghunt.html index 48d7d241..c6571be5 100644 --- a/htdocs/bugs/reghunt.html +++ b/htdocs/bugs/reghunt.html @@ -149,14 +149,14 @@ of this document. Identify the patch -The following https://gcc.gnu.org/wiki/SvnHelp;>SVN -commands are particularly useful to help you identify changes from -one version of a file to another: +The following commands are particularly useful to help you identify +changes from one version of a file to another: -svn diff --help -svn log --help -svn annotate --help +git log --help +git diff --help +git show --help +git annotate --help When you've identified the likely patch out of a set of patches -- 2.24.1
[wwwdocs] You can also retrieve our sources using Git.
And this was the last reference to svn.html in our tree. :) Pushed. --- htdocs/releases.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/htdocs/releases.html b/htdocs/releases.html index 30b777f4..1c8e87e2 100644 --- a/htdocs/releases.html +++ b/htdocs/releases.html @@ -22,8 +22,7 @@ As one option, there are https://gcc.gnu.org/install/binaries.html;>pre-compiled binaries. for various platforms. -You can also retrieve the current development sources -using SVN. +You can also retrieve our sources using Git. GCC Timeline -- 2.24.1
Re: Updating "regression hunting" to the Git world (was: [wwwdocs] Adjustments of "regression hunting" instructions to the post-SVN world.)
On Mon, 20 Jan 2020, Jonathan Wakely wrote: >> If you have further updates to that page, please go ahead and >> simply make them (or let me know). > It still says "The following SVN commands are ..." Yes, that's another piece I'll tackle today/tomorrow. >> Also contrib/reghunt appears in need of *quite* some updates. >> Or do we want to retire it? > I've never read that web page or looked at contrib/reghunt before, > but most of it can probably be done by 'git bisect' run. The web page > should be rewritten in terms of using git bisect. I can take a stab > at that if nobody else wants to. That would be great, thank you! Gerald
[wwwdocs] PR346 has been resolved; remove it from our projects lists.
Pushed. --- htdocs/projects/index.html | 3 --- 1 file changed, 3 deletions(-) diff --git a/htdocs/projects/index.html b/htdocs/projects/index.html index 26f667bd..282d79eb 100644 --- a/htdocs/projects/index.html +++ b/htdocs/projects/index.html @@ -69,9 +69,6 @@ informed of any substantial projects you intend to work on. revision of POSIX; a script running gcc -std=c99 -pedantic) for systems such as GNU/Linux where GCC is the system compiler. - - Fix the issues discussed in https://gcc.gnu.org/PR346;>PR other/346. Simpler porting -- 2.24.1
[wwwdocs] Polish our page on releases a bit.
We now require a C++ compiler to bootstrap. Short some text here and there. Pushed. Gerald --- htdocs/releases.html | 22 +- 1 file changed, 9 insertions(+), 13 deletions(-) diff --git a/htdocs/releases.html b/htdocs/releases.html index c7a9bf1c..30b777f4 100644 --- a/htdocs/releases.html +++ b/htdocs/releases.html @@ -13,15 +13,14 @@ Download -Source code for GCC releases may be downloaded from our +GCC releases may be downloaded from our mirror sites. -Important: because these are source releases, they will be -of little use to you if you do not already have a C compiler on your -machine. If you don't already have a compiler, you need pre-compiled -binaries. -Our https://gcc.gnu.org/install/binaries.html;>binaries page -has references to pre-compiled binaries for various platforms. +Important: these are source releases, so will be of little +use if you do not already have a C++ compiler installed. +As one option, there are +https://gcc.gnu.org/install/binaries.html;>pre-compiled +binaries. for various platforms. You can also retrieve the current development sources using SVN. @@ -29,12 +28,9 @@ has references to pre-compiled binaries for various platforms. GCC Timeline -The table is sorted by date. Note that starting with version 3.3.4, -we provide bug releases for older release branches for those users -who require a very high degree of stability. - -Please refer to our development plan -for future releases, and an alternative view of the release history. +The table is sorted by date. Please refer to our +development plan for future +releases and an alternative view of the release history. ReleaseRelease date -- 2.24.1
Re: Copy list of development branches from svn.html into git.html
On Thu, 16 Jan 2020, Joseph Myers wrote: > This patch makes a start on making the branch information from > svn.html available in git.html. Thank you, Joseph. That allowed for https://gcc.gnu.org/ml/gcc-patches/2020-01/msg01089.html which was, from what I can tell, the last reference to that part of svn.html. > * At an appropriate point svn.html and svnwrite.html should be > redirected to git.html and gitwrite.html. Until then they should > probably have warnings at the top that the SVN repository is now > read-only and superseded by the Git repository. svnwrite.html already is gone and the web server redirects. There's only few references to svn.html left in our tree which I expect to have resolved today or Monday, so we should be able to add that redirection and remove the old file beginning of next week¹. Gerald ¹ For the continental-European definition of week. :)
Re: New redirects for git
On Mon, 13 Jan 2020, Jakub Jelinek wrote: > Thanks to everybody who have helped with this. Thank you for putting this in place, Jakub! Gerald
Re: [wwwdocs] Updates to contribute.html for git-friendly posting rules
Hi Richard, On Thu, 9 Jan 2020, Richard Earnshaw (lists) wrote: > The thread on gcc@ is now so long and complicated that this proposal > back at the start has dropped off the radar. With the switch now > imminent I'd like to re-propose this change, this time more formally. I wasn't sure *who* would best approve this since it's more a policy question than anything else, but let's unstall this... There's a general note I'd make, partly based on my going through some of our older web contents recently (and "decluttering" some of it), and some specific feedback. The general note is that we've had a tendency to be very specific in some of our policies (see the last hunk of https://gcc.gnu.org/ml/gcc-patches/2020-01/msg01064.html for an example) which can make appear us not very inviting to new blood. That is, if all I wanted is to submit a simple patch for a typo somewhere, how would I feel about our set of instructions, and now this addition? Is there a way to make this more light weight or less complex/ optional for simple contributions? +Email subject lines If I interpret both Merriam-Webster and the OED correctly, "e-mail" is the preferrable spelling? +Your contribution email subject line will become the first line of the +commit message for your patch. ... around paragraphs (throughout). +Classifier + +The classifier identifies the type of contribution, for example a +patch, an RFC (request for comments) or a committed patch (where +approval is not necessary. The classifier should be written in upper +case and surrounded with square brackets. This is the only component +of the email subject line that will not appear in the commit itself. +The classifier may optionally contain a version number (vN) and +a series marker (N/M). Examples are: + + + [PATCH] - a single patch + [PATCH v2] - the second version of a single patch + [PATCH 3/7] - the third patch in a series of seven +patches + [RFC] - a point of discussion, may contain a patch + [COMMITTED] - a patch that has already been committed. + I see a lot of [C++], [aarch64], [fortran], [wwwdocs] ;-),... in our archives. Should this all really move into the remainder of the subject line/ first line of the commit message? I guess this is a key part change as part of your proposal? +Component tags Alternately we could use [PATCH,fortran], [committed,C++],... ? Actually, if we use PATCH, RFC,... for everything else, could COMMITTED be omitted? That feels like a bit of shouting (so if we keep that, at least make it lower case)? +A component tag is a short identifier that identifies the part of the +compiler being modified, this is important as it highlights to Full stop: "...modified. This is..." or, better "...modified. This highlights..." which is shorter. I believe this could benefit from some examples of overall subject lines. In fact, perhaps start with examples and describe the individual components? As for next steps, can you please mail the (updated) proposal to the gcc@ list? Some, even quite prominent contributors, do not follow gcc-patches at all (or not close) and this is bigger policy question that will be interesting to the broad group. Hope this helps, Gerald
Re: [wwwdocs] Remove the last reference to svnwrite.html and retire it.
On Fri, 17 Jan 2020, Gerald Pfeifer wrote: > One step^Wfile at a time; next in line: svn.html. Let's make sure old links to svnwrite.html (externally or from our own archives, say) redirect. Pushed. Gerald - Log - commit e48a9f9ec49f5e3e50e5e614bcfecb9543747441 Author: Gerald Pfeifer Date: Sun Jan 19 14:09:23 2020 +0100 With svnwrite.html retired, redirect to gitwrite.html. diff --git a/htdocs/.htaccess b/htdocs/.htaccess index a28af129..e80d14e4 100644 --- a/htdocs/.htaccess +++ b/htdocs/.htaccess @@ -67,6 +67,7 @@ Redirect permanent /projects.html https://gcc.gnu.org/projects/ Redirect permanent /projects/cxx1z.html https://gcc.gnu.org/projects/cxx-status.html#cxx1z Redirect permanent /projects/web.html https://gcc.gnu.org/about.html Redirect permanent /reghunt-howto.html https://gcc.gnu.org/bugs/reghunt.html +Redirect permanent /svnwrite.html https://gcc.gnu.org/gitwrite.html Redirect permanent /thanks.html https://gcc.gnu.org/onlinedocs/gcc/Contributors.html Redirect permanent /timeline.html https://gcc.gnu.org/releases.html#timeline Redirect permanent /web.html https://gcc.gnu.org/about.html
Updating "regression hunting" to the Git world (was: [wwwdocs] Adjustments of "regression hunting" instructions to the post-SVN world.)
On Sun, 19 Jan 2020, Gerald Pfeifer wrote (on gcc-patches@): > With Git a clone carries the whole repository, so remove instructions > on obtaining a local copy of the repository and related instructions > on SVN usage. I just updated https://gcc.gnu.org/bugs/reghunt.html , mostly by removing obsolete aspects related to SVN: https://gcc.gnu.org/ml/gcc-patches/2020-01/msg01121.html If you have further updates to that page, please go ahead and simply make them (or let me know). Also contrib/reghunt appears in need of *quite* some updates. Or do we want to retire it? Gerald
[wwwdocs] Adjustments of "regression hunting" instructions to the post-SVN world.
With Git a clone carries the whole repository, so remove instructions on obtaining a local copy of the repository and related instructions on SVN usage. On the way remove a web link for the contrib/reghunt scripts since those are in the repository anyway. Pushed. Gerald --- htdocs/bugs/reghunt.html | 54 +++- 1 file changed, 4 insertions(+), 50 deletions(-) diff --git a/htdocs/bugs/reghunt.html b/htdocs/bugs/reghunt.html index d9c92067..48d7d241 100644 --- a/htdocs/bugs/reghunt.html +++ b/htdocs/bugs/reghunt.html @@ -54,9 +54,8 @@ while the range is too large to investigate by hand: The first three steps are described below. They can be automated, -as can the framework for the binary search. The directory https://gcc.gnu.org/svn/gcc/trunk/contrib/reghunt/;> -contrib/reghunt in the GCC repository includes +as can the framework for the binary search. The directory +contrib/reghunt in the GCC repository includes scripts to do this work. There are several short cuts @@ -70,58 +69,13 @@ are simple to work around. Get GCC sources -Get a Local Copy of the GCC repository - -Using rsync to get a local copy of the GCC -repository is highly recommended for regression hunts. You'll -be checking out the tree used for the regression search over and over -again and won't want to affect access times for other GCC developers -who are using the real repository, and it will also be faster for -you. - -The full tree takes a lot of disk space, but it's possible to -exclude directories you won't need for your hunt. If you're already -using a local SVN repository via rsync, -you can make a cut-down version of it that leaves out directories you -don't need for the regression hunt. This makes SVN operations much -quicker, making it worthwhile even if the copy is on the same system. -It's particularly useful if you'll want to copy it to a system that is -low on available disk space. The following, for example, makes a -smaller copy of the repository that can be used for finding C and C++ -compile-time problems and takes only half the disk space as the full -repository. - - -cat EOF rsync_exclude ---exclude=gcc-svn/benchmarks ---exclude=gcc-svn/boehm-gcc ---exclude=gcc-svn/old-gcc ---exclude=gcc-svn/wwwdocs ---exclude=gcc-svn/gcc/libstdc++-v3 ---exclude=gcc-svn/gcc/gcc/ada ---exclude=gcc-svn/gcc/gcc/testsuite -EOF - -tar `cat rsync_exclude` -cf - gcc-svn | gzip gcc-svn.tar.gz - - - Check Out a Working Copy -Check out a local working copy of -GCC from your local repository. If you are not using a local -repository, then check out a working copy using anonymous read-only SVN access. In any case, -use a new working copy that is separate from what you use for +Check out a working copy using Git. +Use a new working copy that is separate from what you use for development or other testing, since it is easy to end up with files in strange states. - Information about checking out specific dates, working with branches and tags, and -inspecting the commit logs is available at the https://gcc.gnu.org/wiki/SvnHelp;>SVN Help pages in the GCC -Wiki. - Branch and release dates -- 2.24.1
[wwwdocs] Remove specifics shared by all of GCC from the main Fortran page.
This was triggered by a reference to SVN and dates back to the very early days for GFortran when it was more of a separate projects. Pushed. Gerald --- htdocs/fortran/index.html | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/htdocs/fortran/index.html b/htdocs/fortran/index.html index 7b6aa805..b7a71de2 100644 --- a/htdocs/fortran/index.html +++ b/htdocs/fortran/index.html @@ -85,11 +85,8 @@ of the front end and run-time library development. We encourage everyone to contribute changes and help test GNU Fortran. GNU Fortran is developed on the mainline of GCC and has been part of the compiler collection -since the 4.0.0 release. We provide read access to our development -sources for everybody by anonymous SVN. If -you do not have SVN access (for instance if you are behind a -firewall prohibiting the SVN protocol), you might want to download -snapshots. +since the 4.0.0 release. + Contributions will be reviewed by at least one of the following people: -- 2.24.1
Re: [PATCH] contrib/download_prerequisites: Use http instead of ftp
On Tue, 12 Nov 2019, Janne Blomqvist wrote: > Convert the download_prerequisites script to use http instead of > ftp. This works better with firewalls, proxies, and so on. It's also > faster, a quick test on my system before patch: Plus common web browsers are starting to deprecate and actually remove support for the FTP protocol. Thank you for making this change, and I've made some associated changes to our web pages, too, this week. If you see any further ones, let's proceed. > Question: Should we in fact use https? I haven't used it since > download_prerequisites checks that the sha512/md5 matches the > ones in the GCC tree, but maybe there are reasons? I don't see a strong case for https over http in this context, but would not be opposed either. Gerald
[committed] Reword a comment in varpool_node::ctor_useable_for_folding_p.
2019-01-18 Gerald Pfeifer * varpool.c (ctor_useable_for_folding_p): Fix grammar. --- gcc/ChangeLog | 4 gcc/varpool.c | 7 --- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/gcc/varpool.c b/gcc/varpool.c index e5d632e0eb5..458cdf1bf37 100644 --- a/gcc/varpool.c +++ b/gcc/varpool.c @@ -352,9 +352,10 @@ varpool_node::ctor_useable_for_folding_p (void) return DECL_INITIAL (real_node->decl) != NULL; } - /* Alias of readonly variable is also readonly, since the variable is stored - in readonly memory. We also accept readonly aliases of non-readonly - locations assuming that user knows what he is asking for. */ + /* An alias of a read-only variable is also read-only, since the variable + is stored in read-only memory. We also accept read-only aliases of + non-read-only locations assuming that the user knows what he is asking + for. */ if (!TREE_READONLY (decl) && !TREE_READONLY (real_node->decl)) return false; -- 2.24.1
Re: [Patch, Fortran + wwwdocs] PR93253 – Document BOZ changes, make it friendlier in legacy code
On Wed, 15 Jan 2020, Tobias Burnus wrote: > Regarding the patch, I enclosed a revised version. I have applied the following markup fix on top. Not a bug (in HTML 5, it would have been in XHTML), though surely not what you intended... Gerald - Log - commit aa1665da66b064f53e5c99a09894003b53779baa Author: Gerald Pfeifer Date: Sat Jan 18 13:01:10 2020 +0100 Close a list item instead of opening an empty one. diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index 76a4ed9c..66440102 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -276,7 +276,7 @@ a work-in-progress. Some of these extensions are permitted with the -fallow-invalid-boz, where the error is degraded to a warning and the code is compiled as with older gfortran. - + At any optimization level except-Os, gfortran now uses inline packing for arguments instead of calling a library
Re: analyzer branch renamed to "devel/analyzer"
On Wed, 15 Jan 2020, David Malcolm wrote: > The new git server doesn't seem to like such branch names [1], so I'm > now using "devel/analyzer" Do you plan to also document this in git.html (per the message below you quoted ;-)? > remote: *** Shared development branches should be named devel/*, and > should be documented in https://gcc.gnu.org/git.html . Gerald
[wwwdocs] Have the projects list refer to Git instead of SVN for branches.
Pushed. Gerald --- htdocs/projects/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/projects/index.html b/htdocs/projects/index.html index 2c6472cc..26f667bd 100644 --- a/htdocs/projects/index.html +++ b/htdocs/projects/index.html @@ -23,7 +23,7 @@ help develop GCC: Projects for the GCC web pages. Projects for improving the GCC documentation. -There are several development +There are several development branches with projects that you may be able to help out with. Investigate and fix some of the known optimizer inadequacies. -- 2.24.1
[wwwdocs] Condense and trim three aspects of our snapshot instructions.
This includes folding in a reference to our lists overview as a link into some other text, removing a long obsolete reference to age-old versions of the patch command, and skippking details that are covered by the gcc_update script. Pushed. Gerald --- htdocs/snapshots.html | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/htdocs/snapshots.html b/htdocs/snapshots.html index 80d61e27..6567a857 100644 --- a/htdocs/snapshots.html +++ b/htdocs/snapshots.html @@ -21,20 +21,15 @@ progress. Any given snapshot may generate incorrect code or even fail to build. If you plan on downloading and using snapshots, we highly recommend you -subscribe to the GCC mailing lists. See -mailing lists on the main GCC page for instructions on how to subscribe. +subscribe to the GCC mailing lists. When using the diff files to update from older snapshots to newer snapshots, make sure to use "-E" and "-p" arguments to patch so that empty files are -deleted and full pathnames are provided to patch. If your version of -patch does not support "-E", you'll need to get a newer version. Also note -that you may need autoconf, autoheader and various other programs if you use -diff files to update from one snapshot to the next. +deleted and full pathnames are provided to patch. contrib/gcc_update can be used to apply diffs between successive snapshot versions and preserve relations between generated -files so that autoconf et al aren't needed. This is documented in -comments in contrib/gcc_update. +files so that autoconf et al aren't needed. The program sha512sum which is included with the https://www.gnu.org/software/coreutils/;>GNU Coreutils -- 2.24.1
Re: [wwwdocs] Generalize instructions and remove notes on repository mirroring via rsync.
[ gcc-patches -> gcc ] On Sat, 18 Jan 2020, Gerald Pfeifer wrote: > Remove all references how to perform local checkouts, to SVN, and > mirroring the repository. Instead generalize descriptions since > with the move to Git syncing the repository with rsync and then > checking out locally became mostly pointless. The rsync overview shows gcc-svn gcc svn repository () gcc-cvs gcc cvs repository () I assume it's intentional that git is not listed there? Should gcc-cvs really be listed there still? (If no, should we at this point prune the old CVS tree on the server?) Gerald
[wwwdocs] Generalize instructions and remove notes on repository mirroring via rsync.
Remove all references how to perform local checkouts, to SVN, and mirroring the repository. Instead generalize descriptions since with the move to Git syncing the repository with rsync and then checking out locally became mostly pointless. Pushed. Gerald --- htdocs/rsync.html | 45 - 1 file changed, 12 insertions(+), 33 deletions(-) diff --git a/htdocs/rsync.html b/htdocs/rsync.html index 29e804ac..18700f58 100644 --- a/htdocs/rsync.html +++ b/htdocs/rsync.html @@ -4,7 +4,7 @@ - + GCC: Anonymous read-only rsync access https://gcc.gnu.org/gcc.css; /> @@ -12,47 +12,26 @@ GCC: Anonymous read-only rsync access -We are offering our SVN repository and various other data like our FTP -site through anonymous https://rsync.samba.org;>rsync. +We are offering aspects like our mailing list archives, downloads, +etc. through anonymous https://rsync.samba.org;>rsync. +A list of available rsync targets is available via: -That way you can make local copies of the GCC SVN repository to ease -the burden on the GCC main site, and browse the source locally. - -Getting a local copy of GCC repository using rsync - -The GCC repository is available at rsync://gcc.gnu.org/gcc-svn. -As of January 2011 it consumes about 23GB of disk space which takes a -substantial time to transfer. -Subsequent synchronizations will be much faster, as rsync uses a smart -algorithm to only transfer differences. - -Here is how you get a copy of the repository: -rsync --archive --delete --compress rsync://gcc.gnu.org/gcc-svn /usr/local/gcc-local-repo +rsync rsync://gcc.gnu.org/ -The same command can be run periodically to synchronize your copy of -the repository. -Other rsync options that you might want to use include ---verbose and --progress to provide feedback, -including during the initial phase that is otherwise silent. +To obtain a copy of one of the modules: -To get a list of available rsync targets, run: -rsync rsync://gcc.gnu.org/ +rsync --archive --delete --compress rsync://gcc.gnu.org/MODULE /my/local/directory +The same command can be run periodically to synchronize your local +copy. -Using the local repository - -Refer to SVN instructions to check out your -local copy of the repository. Note that the rsync command above will -mirror the repository at its root directory, so the URL you will need -to use to check out from your local repository will look something -like file:///usr/local/gcc-local-repo/ instead of -svn://gcc.gnu.org/svn/gcc/ (i.e., without the trailing -/svn/gcc directory names that would be included for -gcc.gnu.org access). +Other rsync options that you might want to use include +--verbose and --progress to provide feedback, +including during the initial phase that is otherwise silent. -- 2.24.1
[wwwdocs,C++] Update notes on C++17 and C++2a support.
Streamline these two sections, remove references to svn.html, note the latter has landed by now. Pushed. Jonathan, Marek, Jason, it might be good if you could go through the page and see whether there are similar simplifications/updates. Thanks, Gerald --- htdocs/projects/cxx-status.html | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html index dd3702dc..8d9dbce6 100644 --- a/htdocs/projects/cxx-status.html +++ b/htdocs/projects/cxx-status.html @@ -36,9 +36,7 @@ GCC has experimental support for the next revision of the C++ standard, which is expected to be published in 2020. - C++2a features are available as part of "mainline" GCC -in the trunk of GCC's repository -and will be available in GCC 8 and later. To enable C++2a + C++2a features are available since GCC 8. To enable C++2a support, add the command-line parameter -std=c++2a to your g++ command line. Or, to enable GNU extensions in addition to C++2a features, @@ -462,9 +460,7 @@ https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2017;>the library documentation. - C++17 features are available as part of "mainline" GCC -in the trunk of GCC's repository -and in GCC 5 and later. To enable C++17 + C++17 features are available since GCC 5. To enable C++17 support, add the command-line parameter -std=c++17 to your g++ command line. Or, to enable GNU extensions in addition to C++17 features, -- 2.24.1
[wwwdocs] Refer to Git (not SVN) to obtain current sources.
Pushed. Gerald --- htdocs/snapshots.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/snapshots.html b/htdocs/snapshots.html index 3c491b00..80d61e27 100644 --- a/htdocs/snapshots.html +++ b/htdocs/snapshots.html @@ -11,7 +11,7 @@ GCC Snapshots -We recommend that you use SVN to access our +We recommend that you use Git to access our current development sources. We also make regular snapshots available for download from our -- 2.24.1
[wwwdocs] Fix up formatting of one sentence in the main Fortran page.
Pushed. Gerald --- htdocs/fortran/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/fortran/index.html b/htdocs/fortran/index.html index 42012ddc..7b6aa805 100644 --- a/htdocs/fortran/index.html +++ b/htdocs/fortran/index.html @@ -30,7 +30,7 @@ this to attract a diverse team of developers and to ensure that GFortran works on multiple architectures and diverse environments. We always need more help. If you are interested in participating, please contact us at mailto:fort...@gcc.gnu.org;>fort...@gcc.gnu.org. -(Also check out our mailing lists page) +(Also check out our mailing lists page.) The Wiki and Getting the Compiler -- 2.24.1
