public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vcunat at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/57125] Build not SMP safe; fails to build bconfig.h Date: Fri, 03 Jan 2014 09:23:00 -0000 [thread overview] Message-ID: <bug-57125-4-qRbOm6y7f5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57125-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57125 Vladimír Čunát <vcunat at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vcunat at gmail dot com --- Comment #2 from Vladimír Čunát <vcunat at gmail dot com> --- In this matter I'm quite confused by the intentions of http://gcc.gnu.org/ml/gcc-patches/2012-07/msg00273.html It states that host object files depend on CONFIG_H, but these seem to get in fact built with -DGENERATOR_FILE (according to build log), so through gentype.c, they include bconfig.h instead of config.h. I don't see that reflected in build dependencies, and more importantly, I'm not even sure this consequence was intended/correct. >From gcc-bugs-return-438964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 09:23:05 2014 Return-Path: <gcc-bugs-return-438964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 21947 invoked by alias); 3 Jan 2014 09:23:05 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 21894 invoked by uid 48); 3 Jan 2014 09:23:02 -0000 From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/59519] [4.9 Regression] ICE on valid code at -O3 on x86_64-linux-gnu in slpeel_update_phi_nodes_for_guard1, at tree-vect-loop-manip.c:486 Date: Fri, 03 Jan 2014 09:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59519-4-mgtDRCvEU7@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59519-4@http.gcc.gnu.org/bugzilla/> References: <bug-59519-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-01/txt/msg00106.txt.bz2 Content-length: 1007 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY519 --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to bin.cheng from comment #7) > (In reply to Jakub Jelinek from comment #6) > > Created attachment 31562 [details] > > gcc49-pr59519.patch > > > > I wonder if this isn't just a checking issue, the two PHI nodes created in > > *new_exit_bb have the same argument, so I think it is just fine if the two > > PHI results are used interchangeably, later optimization passes should > > hopefully coalesce them into a single IV. > > I tested one similar patch before. It passed x86_64 bootstrap and normal > regression test. It failed some ada (also one go) cases if I ran regression > test with "-O3" option. The failures look like noise to me, which I am not > sure about. What's your test results? I admit I haven't performed -O3 bootstrap but normal, saw no bootstrap failures nor testsuite regressions. I'll try to run make check with RUNTESTFLAGS='--target_board=unix/-O3'.
next prev parent reply other threads:[~2014-01-03 9:23 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-30 12:30 [Bug bootstrap/57125] New: " enrico.scholz at informatik dot tu-chemnitz.de 2013-10-12 5:42 ` [Bug bootstrap/57125] " dirtyepic at gentoo dot org 2014-01-03 9:23 ` vcunat at gmail dot com [this message] 2014-03-24 17:59 ` vbraun at physics dot upenn.edu 2014-03-25 4:05 ` dirtyepic at gentoo dot org 2014-08-29 20:58 ` andrew at ado dot is-a-geek.net 2014-08-29 22:15 ` andrew at ado dot is-a-geek.net 2014-11-05 22:54 ` dev at codyps dot com 2015-03-31 8:07 ` vapier at gentoo dot org 2015-08-10 10:10 ` vapier at gentoo dot org 2021-09-11 22:58 ` pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-57125-4-qRbOm6y7f5@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).