* FW: Build failed in Jenkins: BuildThunderX_native_gcc_upstream #1267 [not found] <258866171.579.1489773600679.JavaMail.jenkins@blackduck> @ 2017-03-17 18:39 ` Pinski, Andrew 2017-03-17 18:48 ` Bernd Schmidt 0 siblings, 1 reply; 8+ messages in thread From: Pinski, Andrew @ 2017-03-17 18:39 UTC (permalink / raw) To: gcc; +Cc: law, bschmidt One of the following revision caused a bootstrap comparison failure on aarch64-linux-gnu: r246225 r246226 r246227 Thanks, Andrew Pinski Ignore the URLs in the log file below, this is a Jenkins to Cavium. -----Original Message----- From: jenkins@cavium.com [mailto:jenkins@cavium.com] Sent: Friday, March 17, 2017 11:00 AM To: Pinski, Andrew <Andrew.Pinski@cavium.com> Subject: Build failed in Jenkins: BuildThunderX_native_gcc_upstream #1267 ------------------------------------------ rm -f stage_current make[3]: Leaving directory '<http://toolchain-releases.caveonetworks.com:8080/job/BuildThunderX_native_gcc_upstream/ws/objdir'> Comparing stages 2 and 3 Bootstrap comparison failure! gcc/lto/lto.o differs libcpp/line-map.o differs Makefile:24072: recipe for target 'compare' failed make[2]: *** [compare] Error 1 make[2]: Leaving directory '<http://toolchain-releases.caveonetworks.com:8080/job/BuildThunderX_native_gcc_upstream/ws/objdir'> Makefile:24051: recipe for target 'stage3-bubble' failed make[1]: *** [stage3-bubble] Error 2 make[1]: Leaving directory '<http://toolchain-releases.caveonetworks.com:8080/job/BuildThunderX_native_gcc_upstream/ws/objdir'> Makefile:931: recipe for target 'all' failed make: *** [all] Error 2 Build step 'Execute shell' marked build as failure [WARNINGS] Skipping publisher since build result is FAILURE Archiving artifacts ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: FW: Build failed in Jenkins: BuildThunderX_native_gcc_upstream #1267 2017-03-17 18:39 ` FW: Build failed in Jenkins: BuildThunderX_native_gcc_upstream #1267 Pinski, Andrew @ 2017-03-17 18:48 ` Bernd Schmidt 2017-03-17 19:33 ` Jeff Law 2017-03-17 21:31 ` Andrew Pinski 0 siblings, 2 replies; 8+ messages in thread From: Bernd Schmidt @ 2017-03-17 18:48 UTC (permalink / raw) To: Pinski, Andrew, gcc; +Cc: law On 03/17/2017 07:38 PM, Pinski, Andrew wrote: > One of the following revision caused a bootstrap comparison failure on aarch64-linux-gnu: > r246225 > r246226 > r246227 Can you help narrow that down? Bernd ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: FW: Build failed in Jenkins: BuildThunderX_native_gcc_upstream #1267 2017-03-17 18:48 ` Bernd Schmidt @ 2017-03-17 19:33 ` Jeff Law 2017-03-17 21:31 ` Andrew Pinski 1 sibling, 0 replies; 8+ messages in thread From: Jeff Law @ 2017-03-17 19:33 UTC (permalink / raw) To: Bernd Schmidt, Pinski, Andrew, gcc On 03/17/2017 12:47 PM, Bernd Schmidt wrote: > On 03/17/2017 07:38 PM, Pinski, Andrew wrote: >> One of the following revision caused a bootstrap comparison failure on >> aarch64-linux-gnu: >> r246225 >> r246226 >> r246227 > > Can you help narrow that down? I'm provisioning an aarch64 system now. jeff ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: FW: Build failed in Jenkins: BuildThunderX_native_gcc_upstream #1267 2017-03-17 18:48 ` Bernd Schmidt 2017-03-17 19:33 ` Jeff Law @ 2017-03-17 21:31 ` Andrew Pinski 2017-03-17 22:28 ` Jeff Law 1 sibling, 1 reply; 8+ messages in thread From: Andrew Pinski @ 2017-03-17 21:31 UTC (permalink / raw) To: Bernd Schmidt; +Cc: Pinski, Andrew, gcc, law On Fri, Mar 17, 2017 at 11:47 AM, Bernd Schmidt <bschmidt@redhat.com> wrote: > On 03/17/2017 07:38 PM, Pinski, Andrew wrote: >> >> One of the following revision caused a bootstrap comparison failure on >> aarch64-linux-gnu: >> r246225 >> r246226 >> r246227 > > > Can you help narrow that down? I can though I don't want to duplicate work since Jeff was going to provision an aarch64 system. My automated testing is approximately every hour or so; these commits were within an hour window even. I did not look into the revisions when I write the email but I suspect r246227 did NOT cause it since aarch64 does not use reload anymore. Thanks, Andrew > > > Bernd > ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: FW: Build failed in Jenkins: BuildThunderX_native_gcc_upstream #1267 2017-03-17 21:31 ` Andrew Pinski @ 2017-03-17 22:28 ` Jeff Law 2017-03-17 23:12 ` Jim Wilson 0 siblings, 1 reply; 8+ messages in thread From: Jeff Law @ 2017-03-17 22:28 UTC (permalink / raw) To: Andrew Pinski, Bernd Schmidt; +Cc: Pinski, Andrew, gcc On 03/17/2017 03:31 PM, Andrew Pinski wrote: > On Fri, Mar 17, 2017 at 11:47 AM, Bernd Schmidt <bschmidt@redhat.com> wrote: >> On 03/17/2017 07:38 PM, Pinski, Andrew wrote: >>> >>> One of the following revision caused a bootstrap comparison failure on >>> aarch64-linux-gnu: >>> r246225 >>> r246226 >>> r246227 >> >> >> Can you help narrow that down? > > I can though I don't want to duplicate work since Jeff was going to > provision an aarch64 system. My automated testing is approximately > every hour or so; these commits were within an hour window even. > I did not look into the revisions when I write the email but I suspect > r246227 did NOT cause it since aarch64 does not use reload anymore. My the box I got isn't terribly fast, but regardless I'll be walking through each commit to see if I can trigger the failure. 246224 tested OK (as it should). 246225 is in progress. jeff > ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: FW: Build failed in Jenkins: BuildThunderX_native_gcc_upstream #1267 2017-03-17 22:28 ` Jeff Law @ 2017-03-17 23:12 ` Jim Wilson 2017-03-17 23:51 ` Jim Wilson 0 siblings, 1 reply; 8+ messages in thread From: Jim Wilson @ 2017-03-17 23:12 UTC (permalink / raw) To: Jeff Law, Andrew Pinski, Bernd Schmidt; +Cc: Pinski, Andrew, gcc On 03/17/2017 03:28 PM, Jeff Law wrote: > On 03/17/2017 03:31 PM, Andrew Pinski wrote: >> On Fri, Mar 17, 2017 at 11:47 AM, Bernd Schmidt <bschmidt@redhat.com> >> wrote: >>> On 03/17/2017 07:38 PM, Pinski, Andrew wrote: >>>> >>>> One of the following revision caused a bootstrap comparison failure on >>>> aarch64-linux-gnu: >>>> r246225 >>>> r246226 >>>> r246227 >>> >>> >>> Can you help narrow that down? >> >> I can though I don't want to duplicate work since Jeff was going to >> provision an aarch64 system. My automated testing is approximately >> every hour or so; these commits were within an hour window even. >> I did not look into the revisions when I write the email but I suspect >> r246227 did NOT cause it since aarch64 does not use reload anymore. > My the box I got isn't terribly fast, but regardless I'll be walking > through each commit to see if I can trigger the failure. > > 246224 tested OK (as it should). > > 246225 is in progress. I have access to a fast box that isn't otherwise in use at the moment so I'm taking a look. r246225 builds OK. r246226 does not. So it is Bernd's combine patch. A little experimenting shows that the compare difference is triggered by the use of -gtoggle in stage2, which is not used in stage3. Otherwise stage2 and stage3 generate identical code. The bug is apparently due to a problem with handling debug insns in the combine patch. Jim ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: FW: Build failed in Jenkins: BuildThunderX_native_gcc_upstream #1267 2017-03-17 23:12 ` Jim Wilson @ 2017-03-17 23:51 ` Jim Wilson 2017-03-18 1:32 ` Jeff Law 0 siblings, 1 reply; 8+ messages in thread From: Jim Wilson @ 2017-03-17 23:51 UTC (permalink / raw) To: Jeff Law, Andrew Pinski, Bernd Schmidt; +Cc: Pinski, Andrew, gcc On 03/17/2017 04:12 PM, Jim Wilson wrote: > I have access to a fast box that isn't otherwise in use at the moment so > I'm taking a look. r246225 builds OK. r246226 does not. So it is > Bernd's combine patch. A little experimenting shows that the compare > difference is triggered by the use of -gtoggle in stage2, which is not > used in stage3. Otherwise stage2 and stage3 generate identical code. > The bug is apparently due to a problem with handling debug insns in the > combine patch. Changing a new prev_nonnote_insn call to a prev_nonnote_nondebug_insn call appears to solve the problem. I will have to do a bootstrap and make check from scratch to verify. I also noticed that there is a redundant i1 check in the patch which should be fixed also. Jim ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: FW: Build failed in Jenkins: BuildThunderX_native_gcc_upstream #1267 2017-03-17 23:51 ` Jim Wilson @ 2017-03-18 1:32 ` Jeff Law 0 siblings, 0 replies; 8+ messages in thread From: Jeff Law @ 2017-03-18 1:32 UTC (permalink / raw) To: Jim Wilson, Andrew Pinski, Bernd Schmidt; +Cc: Pinski, Andrew, gcc On 03/17/2017 05:51 PM, Jim Wilson wrote: > On 03/17/2017 04:12 PM, Jim Wilson wrote: >> I have access to a fast box that isn't otherwise in use at the moment so >> I'm taking a look. r246225 builds OK. r246226 does not. So it is >> Bernd's combine patch. A little experimenting shows that the compare >> difference is triggered by the use of -gtoggle in stage2, which is not >> used in stage3. Otherwise stage2 and stage3 generate identical code. >> The bug is apparently due to a problem with handling debug insns in the >> combine patch. > > Changing a new prev_nonnote_insn call to a prev_nonnote_nondebug_insn > call appears to solve the problem. I will have to do a bootstrap and > make check from scratch to verify. I also noticed that there is a > redundant i1 check in the patch which should be fixed also. Thanks Jim. My 246226 was just spinning up. Consider your fixes pre-approved. jeff ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2017-03-18 1:32 UTC | newest] Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <258866171.579.1489773600679.JavaMail.jenkins@blackduck> 2017-03-17 18:39 ` FW: Build failed in Jenkins: BuildThunderX_native_gcc_upstream #1267 Pinski, Andrew 2017-03-17 18:48 ` Bernd Schmidt 2017-03-17 19:33 ` Jeff Law 2017-03-17 21:31 ` Andrew Pinski 2017-03-17 22:28 ` Jeff Law 2017-03-17 23:12 ` Jim Wilson 2017-03-17 23:51 ` Jim Wilson 2017-03-18 1:32 ` Jeff Law
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).