public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bernds at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/54688] [4.8 regression] violation of implicit restriction "No_Elaboration_Code" on a-ioexce.ads Date: Wed, 26 Sep 2012 13:50:00 -0000 [thread overview] Message-ID: <bug-54688-4-3ZN7EqC1Eb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54688-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54688 --- Comment #7 from Bernd Schmidt <bernds at gcc dot gnu.org> 2012-09-26 13:50:06 UTC --- Oh, I missed that it was a MINUS rtx. This is noncanonical RTL, it should be (plus (sp) (negated constant)). Does the bug persist if you fix the sparc port in this way?
next prev parent reply other threads:[~2012-09-26 13:50 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-24 7:44 [Bug ada/54688] New: [4.8 regression] a-ioexce.ads violation of implicit restriction "No_Elaboration_Code" breaks Ada bootstrap on sparc64-linux mikpe at it dot uu.se 2012-09-24 19:05 ` [Bug bootstrap/54688] [4.8 regression] violation of implicit restriction "No_Elaboration_Code" on a-ioexce.ads ebotcazou at gcc dot gnu.org 2012-09-24 19:15 ` ebotcazou at gcc dot gnu.org 2012-09-26 11:44 ` ebotcazou at gcc dot gnu.org 2012-09-26 12:56 ` ro at gcc dot gnu.org 2012-09-26 13:19 ` bernds at gcc dot gnu.org 2012-09-26 13:37 ` ebotcazou at gcc dot gnu.org 2012-09-26 13:50 ` bernds at gcc dot gnu.org [this message] 2012-09-26 14:03 ` ebotcazou at gcc dot gnu.org 2012-09-26 14:14 ` bernds at gcc dot gnu.org 2012-09-27 7:57 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-09-27 13:28 ` bernds at gcc dot gnu.org 2012-09-27 16:00 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-09-28 7:56 ` ebotcazou at gcc dot gnu.org 2012-09-28 20:33 ` bernds at gcc dot gnu.org 2012-09-28 20:46 ` ebotcazou 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-54688-4-3ZN7EqC1Eb@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).