public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/53058] New: Another ice in remove_range_assertions Date: Sat, 21 Apr 2012 09:09:00 -0000 [thread overview] Message-ID: <bug-53058-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53058 Bug #: 53058 Summary: Another ice in remove_range_assertions Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: dcb314@hotmail.com Created attachment 27211 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27211 C source code I just tried to compile the package quake3-1.36-13 on gcc-4.8 trunk dated 20120418 on an AMD x86_64 box. The compiler said code/botlib/be_ai_move.c: In function 'BotFuncBobStartEnd': code/botlib/be_ai_move.c:2227:6: internal compiler error: in remove_range_assertions, at tree-vrp.c:5937 void BotFuncBobStartEnd(aas_reachability_t *reach, vec3_t start, vec3_t end, vec3_t origin) ^ Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Preprocessed source code attached. Flag -O2 required.
next reply other threads:[~2012-04-21 9:09 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-21 9:09 dcb314 at hotmail dot com [this message] 2012-04-21 11:37 ` [Bug c/53058] " markus at trippelsdorf dot de 2012-04-22 13:02 ` markus at trippelsdorf dot de 2012-04-23 10:36 ` [Bug tree-optimization/53058] [4.8 Regression] " rguenth at gcc dot gnu.org 2012-04-23 10:40 ` jakub at gcc dot gnu.org 2012-04-23 14:17 ` jakub at gcc dot gnu.org 2012-04-25 11:36 ` jakub at gcc dot gnu.org 2012-04-25 11:51 ` jakub 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-53058-4@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).