Re: New mklog script
On 5/26/20 8:06 PM, Jason Merrill wrote:
gcc-ci-log would be better if you want something short; I'd prefer
gcc-commit-mklog, and let people define their own shorter aliases as desired.
Hello.
There's a rename I'm going to install.
Martin
>From b423f910dcc2a58a86b61cc5b966a81066abbf12 Mon Sep 17 00:00:00 2001
From: Martin Liska
Date: Wed, 27 May 2020 10:16:21 +0200
Subject: [PATCH] Rename commit-mklog alias to gcc-commit-mklog.
contrib/ChangeLog:
* gcc-git-customization.sh: Rename
commit-mklog to gcc-commit-mklog.
---
contrib/gcc-git-customization.sh | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/contrib/gcc-git-customization.sh b/contrib/gcc-git-customization.sh
index dcc42683fa6..0e56dcf9873 100755
--- a/contrib/gcc-git-customization.sh
+++ b/contrib/gcc-git-customization.sh
@@ -27,10 +27,8 @@ git config alias.gcc-undescr \!"f() { o=\$(git config --get gcc-config.upstream)
git config alias.gcc-verify '!f() { "`git rev-parse --show-toplevel`/contrib/gcc-changelog/git_check_commit.py" $@; } ; f'
git config alias.gcc-backport '!f() { rev=$1; git cherry-pick -x $@; } ; f'
-
git config alias.gcc-mklog '!f() { "`git rev-parse --show-toplevel`/contrib/mklog.py" $@; } ; f'
-
-git config alias.commit-mklog '!f() { GCC_FORCE_MKLOG=1 git commit "$@"; }; f'
+git config alias.gcc-commit-mklog '!f() { GCC_FORCE_MKLOG=1 git commit "$@"; }; f'
# Make diff on MD files use "(define" as a function marker.
# Use this in conjunction with a .gitattributes file containing
--
2.26.2
Re: New mklog script
On 5/26/20 5:38 PM, Martin Sebor wrote: By the way, it's nice that the existing gcc- aliases are documented on https://gcc.gnu.org/gitwrite.html. I would suggest to add this one there as well. Yes. I added the documentation bit and pushed ho master. Martin >From 035bdc56110914329c860870e338463793fb5597 Mon Sep 17 00:00:00 2001 From: Martin Liska Date: Wed, 27 May 2020 10:22:01 +0200 Subject: [PATCH] Document gcc-commit-mklog hook. --- htdocs/gitwrite.html | 2 ++ 1 file changed, 2 insertions(+) diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html index e3a1305b..b9bcb768 100644 --- a/htdocs/gitwrite.html +++ b/htdocs/gitwrite.html @@ -436,6 +436,8 @@ repository: gcc-verify - verify ChangeLog format for a particular commit gcc-backport - alias for git cherry-pick -x gcc-mklog - generate a ChangeLog template for a patch + gcc-commit-mklog - commit a git revision with a pre-filled + ChangeLog template The final customization that the script makes is to add a diff rule so -- 2.26.2
Invalid Delivery Address
gccWe Attempted to deliver your item on MAY 27. 2020 but could not complete the delivery because the dispatch rider did not have access to the location due to covid19 pandemic.Please kindly check the link below for instruction on how to pick your package.AWB-579936522. DELIVERY INFORMATION Scheduled date for delivery MAY 27, 2020 Delivery time Pending correction CLICK HERE to confirm if your address iscorrect, before sending it to our sales office to send it to its destination.Regards,Caroline SativCustomer Support2020 © DHL International GmbH. All rights.. .. ...DHL Global Mail DHL Global Mail es su especialista para Business Mail internacional, B2C Parcel,Direct Marketing, and Hybrid or fully Digital Services. With our internationalpostal solutions, we are dedicated to making our customers' lives easier. Virus-free. www.avast.com
CCTV camera customers: Update Profile
We received a request to change your subscription preferences for CCTV camera customers. If you made this request, and would like to change your preferences, use the link below Update your preferences (https://us15.mailchimp.com/mctx/clicks?url=https%3A%2F%2Fzysecurity.us15.list-manage.com%2Fprofile%3Fu%3D180ff4e1e8d2da3c75d9a68d4%26id%3D01b0171922%26e%3D0d7ddca964%26token%3D180ff4e1e8d2da3c75d9a68d4-83d055590d0b3b328333e1591b39af18-1590575935_f28653b8ab870165a6f9de1bc52f2d339c8fbdd403b9d4bf3eddeb6667e5bc5b&h=08f65d03f7f08780f793cf9b65f27a6ef35bac1fb0276a3ad0eec93a4754a28b&v=1&xid=1d18f0b180&uid=69093105&pool=contact_facing&subject=CCTV+camera+customers%3A+Update+Profile) If you did not make this request, it was probably submitted by someone else by mistake. You can ignore this email, and no changes will be made to your subscription preferences. For questions about this list, please contact: jan...@zysecuritytech.com (mailto:jan...@zysecuritytech.com)
git gcc-backport.py : No such file or directory
Hi Martin, currently, doing git gcc-backport from a gcc9 branch results in $ git gcc-backport r11-588-g8df7ee67f6fdc780e9453f2baa8d1bf62c000761 environment: /home/ig25/Gcc/gcc9/contrib/git-backport.py: No such file or directory Would it make sense to push the git-backport.py file to the release branches, as well? Regards Thomas
Re: git gcc-backport.py : No such file or directory
On 5/27/20 4:11 PM, Thomas Koenig wrote: Hi Martin, currently, doing git gcc-backport from a gcc9 branch results in $ git gcc-backport r11-588-g8df7ee67f6fdc780e9453f2baa8d1bf62c000761 environment: /home/ig25/Gcc/gcc9/contrib/git-backport.py: No such file or directory Would it make sense to push the git-backport.py file to the release branches, as well? Yes, I'm aware of the limitation and let me do it now. Thanks for reminder, Martin Regards Thomas
Re: GCC Testsuite patches break AIX
Hello, David, On May 26, 2020, David Edelsohn wrote: > Complaints about -dA, -dD, -dumpbase, etc. This was the main symptom of the problem fixed in the follow-up commit r11-635-g6232d02b4fce4c67d39815aa8fb956e4b10a4e1b Could you please confirm that you did NOT have this commit in your failing build, and that the patch above fixes the problem for you as it did for others? > This patch was not properly tested on all targets. This problem had nothing to do with targets. Having Ada enabled, which I've nearly always and very long done to increase test coverage, was what kept the preexisting bug latent in my testing. Sorry that I failed to catch it before the initial check in. -- Alexandre Oliva, freedom fighterhe/himhttps://FSFLA.org/blogs/lxo/ Free Software Evangelist Stallman was right, but he's left :( GNU Toolchain Engineer Live long and free, and prosper ethically
Re: git gcc-backport.py : No such file or directory
On 5/27/20 4:13 PM, Martin Liška wrote: Yes, I'm aware of the limitation and let me do it now. I've just backported the script to all active branches. Please try it. Martin
Re: GCC Testsuite patches break AIX
On Wed, 2020-05-27 at 11:16 -0300, Alexandre Oliva wrote:
> Hello, David,
>
> On May 26, 2020, David Edelsohn wrote:
>
> > Complaints about -dA, -dD, -dumpbase, etc.
>
> This was the main symptom of the problem fixed in the follow-up commit
> r11-635-g6232d02b4fce4c67d39815aa8fb956e4b10a4e1b
>
> Could you please confirm that you did NOT have this commit in your
> failing build, and that the patch above fixes the problem for you as it
> did for others?
>
>
> > This patch was not properly tested on all targets.
>
> This problem had nothing to do with targets. Having Ada enabled, which
> I've nearly always and very long done to increase test coverage, was
> what kept the preexisting bug latent in my testing.
>
>
> Sorry that I failed to catch it before the initial check in.
Any thoughts on the massive breakage on the embedded ports in the testsuite?
Essentially every test that links is failing like this:
> Executing on host: /home/jenkins/workspace/c6x-elf/c6x-elf-obj/gcc/gcc/xgcc
> -B/home/jenkins/workspace/c6x-elf/c6x-elf-obj/gcc/gcc/
> /home/jenkins/gcc/gcc/testsuite/gcc.c-torture/execute/2112-1.c
> gcc_tg.o-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
> -fdiagnostics-color=never -fdiagnostics-urls=never-O0 -w -msim {} {}
> -
> Wl,-wrap,exit -Wl,-wrap,_exit -Wl,-wrap,main -Wl,-wrap,abort -lm -o
> ./2112-1.exe(timeout = 300)
> spawn -ignore SIGHUP /home/jenkins/workspace/c6x-elf/c6x-elf-obj/gcc/gcc/xgcc
> -B/home/jenkins/workspace/c6x-elf/c6x-elf-obj/gcc/gcc/
> /home/jenkins/gcc/gcc/testsuite/gcc.c-torture/execute/2112-1.c gcc_tg.o
> -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers -fdiagnostics-
> color=never -fdiagnostics-urls=never -O0 -w -msim -Wl,-wrap,exit -Wl,-
> wrap,_exit -Wl,-wrap,main -Wl,-wrap,abort -lm -o ./2112-1.exe^M
> xgcc: error: : No such file or directory^M
> xgcc: error: : No such file or directory^M
> compiler exited with status 1
> FAIL: gcc.c-torture/execute/2112-1.c -O0 (test for excess errors)
> Excess errors:
> xgcc: error: : No such file or directory
> xgcc: error: : No such file or directory
>
Sadly there's no additional output that would help us figure out what went
wrong.
jeff
Re: GCC Testsuite patches break AIX
On Wed, 27 May 2020 at 16:26, Jeff Law via Gcc wrote:
>
> On Wed, 2020-05-27 at 11:16 -0300, Alexandre Oliva wrote:
> > Hello, David,
> >
> > On May 26, 2020, David Edelsohn wrote:
> >
> > > Complaints about -dA, -dD, -dumpbase, etc.
> >
> > This was the main symptom of the problem fixed in the follow-up commit
> > r11-635-g6232d02b4fce4c67d39815aa8fb956e4b10a4e1b
> >
> > Could you please confirm that you did NOT have this commit in your
> > failing build, and that the patch above fixes the problem for you as it
> > did for others?
> >
> >
> > > This patch was not properly tested on all targets.
> >
> > This problem had nothing to do with targets. Having Ada enabled, which
> > I've nearly always and very long done to increase test coverage, was
> > what kept the preexisting bug latent in my testing.
> >
> >
> > Sorry that I failed to catch it before the initial check in.
> Any thoughts on the massive breakage on the embedded ports in the testsuite?
> Essentially every test that links is failing like this:
>
> > Executing on host: /home/jenkins/workspace/c6x-elf/c6x-elf-obj/gcc/gcc/xgcc
> > -B/home/jenkins/workspace/c6x-elf/c6x-elf-obj/gcc/gcc/
> > /home/jenkins/gcc/gcc/testsuite/gcc.c-torture/execute/2112-1.c
> > gcc_tg.o-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
> > -fdiagnostics-color=never -fdiagnostics-urls=never-O0 -w -msim {}
> > {} -
> > Wl,-wrap,exit -Wl,-wrap,_exit -Wl,-wrap,main -Wl,-wrap,abort -lm -o
> > ./2112-1.exe(timeout = 300)
> > spawn -ignore SIGHUP
> > /home/jenkins/workspace/c6x-elf/c6x-elf-obj/gcc/gcc/xgcc
> > -B/home/jenkins/workspace/c6x-elf/c6x-elf-obj/gcc/gcc/
> > /home/jenkins/gcc/gcc/testsuite/gcc.c-torture/execute/2112-1.c gcc_tg.o
> > -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
> > -fdiagnostics-
> > color=never -fdiagnostics-urls=never -O0 -w -msim -Wl,-wrap,exit -Wl,-
> > wrap,_exit -Wl,-wrap,main -Wl,-wrap,abort -lm -o ./2112-1.exe^M
> > xgcc: error: : No such file or directory^M
> > xgcc: error: : No such file or directory^M
> > compiler exited with status 1
> > FAIL: gcc.c-torture/execute/2112-1.c -O0 (test for excess errors)
> > Excess errors:
> > xgcc: error: : No such file or directory
> > xgcc: error: : No such file or directory
> >
>
>
> Sadly there's no additional output that would help us figure out what went
> wrong.
If that helps, I traced this down to the new gcc_adjust_linker_flags function.
Christophe
>
> jeff
>
Re: git gcc-backport.py : No such file or directory
Hi Martin, On 5/27/20 4:13 PM, Martin Liška wrote: Yes, I'm aware of the limitation and let me do it now. I've just backported the script to all active branches. Please try it. Works without a hitch, thanks! I have just successfully pushed r9-8628 to the gcc-9 branch. Regards Thomas
PCH test errors
I'm testing amdgcn-amdhsa, and I get lot of PCH test failures with errors like this: gcc.dg/pch/common-1.c:1:22: error: one or more PCH files were found, but they were invalid gcc.dg/pch/common-1.c:1:22: error: use -Winvalid-pch for more information gcc.dg/pch/common-1.c:1:10: fatal error: common-1.h: No such file or directory It may affect other targets, but I've not tested those. Has anybody else seen this issue? I've done a bisect, and found it first starts with this: 1dedc12d1: revamp dump and aux output names I've also seen others complaining about other issues with this commit, so this may be a duplicate issue, somehow. Andrew
Re: GCC Testsuite patches break AIX
On Wed, May 27, 2020 at 10:16 AM Alexandre Oliva wrote: > > Hello, David, > > On May 26, 2020, David Edelsohn wrote: > > > Complaints about -dA, -dD, -dumpbase, etc. > > This was the main symptom of the problem fixed in the follow-up commit > r11-635-g6232d02b4fce4c67d39815aa8fb956e4b10a4e1b > > Could you please confirm that you did NOT have this commit in your > failing build, and that the patch above fixes the problem for you as it > did for others? Hi, Alexandre Thanks for diligently working on this issue. I did not have the fix mentioned above in the original test. I am performing a new bootstrap with the patch. Hopefully it will address some or all of the issues. DejaGNU and the GCC testsuite is what it is. It is fragile. One of the strengths of GCC is the wide variety of targets supported, not only GNU/Linux, but other Unixes, Windows, embedded. Testsuite infrastructure changes such as these need testing on a wide variety of targets to find system dependencies. Thanks, David
Re: GCC Testsuite patches break AIX
On May 27, 2020, Christophe Lyon via Gcc wrote:
> On Wed, 27 May 2020 at 16:26, Jeff Law via Gcc wrote:
>> Any thoughts on the massive breakage on the embedded ports in the testsuite?
I wasn't aware of any. Indeed, one of my last steps before submitting
the patchset was to fix problems that had come up in embedded ports,
with gcc_adjust_linker_flags and corresponding changes to outputs.exp
itself.
>> Essentially every test that links is failing like this:
>>
>> > Executing on host: /home/jenkins/workspace/c6x-elf/c6x-elf-obj/gcc/gcc/xgcc
>> > -B/home/jenkins/workspace/c6x-elf/c6x-elf-obj/gcc/gcc/
>> > /home/jenkins/gcc/gcc/testsuite/gcc.c-torture/execute/2112-1.c
>> > gcc_tg.o-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
>> > -fdiagnostics-color=never -fdiagnostics-urls=never-O0 -w -msim {}
>> > {} -
>> > Wl,-wrap,exit -Wl,-wrap,_exit -Wl,-wrap,main -Wl,-wrap,abort -lm -o
>> > ./2112-1.exe(timeout = 300)
>> > spawn -ignore SIGHUP
>> > /home/jenkins/workspace/c6x-elf/c6x-elf-obj/gcc/gcc/xgcc
>> > -B/home/jenkins/workspace/c6x-elf/c6x-elf-obj/gcc/gcc/
>> > /home/jenkins/gcc/gcc/testsuite/gcc.c-torture/execute/2112-1.c gcc_tg.o
>> > -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
>> > -fdiagnostics-
>> > color=never -fdiagnostics-urls=never -O0 -w -msim -Wl,-wrap,exit -Wl,-
>> > wrap,_exit -Wl,-wrap,main -Wl,-wrap,abort -lm -o ./2112-1.exe^M
>> > xgcc: error: : No such file or directory^M
>> Sadly there's no additional output that would help us figure out what went
>> wrong.
> If that helps, I traced this down to the new gcc_adjust_linker_flags function.
Thanks. Yeah, H-P observed and submitted a similar report that made me
wonder about empty arguments being passed to GCC. Jeff's report
confirms the suspicion. See how there are a couple of {}s after -msim
in the "Executing on host" line, that in the "spawn" line are completely
invisible, only suggested by the extra whitespace. That was not quite
visible in H-P's report, but Jeff's makes it clear.
I suppose this means there are consecutive blanks in e.g. board's
ldflags, and the split function is turning each consecutive pair of
blanks into an empty argument. I'm testing a fix (kludge?) in
refs/users/aoliva/heads/testme 169b13d14d3c1638e94ea7e8f718cdeaf88aed65
--
Alexandre Oliva, freedom fighterhe/himhttps://FSFLA.org/blogs/lxo/
Free Software Evangelist Stallman was right, but he's left :(
GNU Toolchain Engineer Live long and free, and prosper ethically
