public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "regehr at cs dot utah dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/38281] New: ice: Segmentation fault Date: Thu, 27 Nov 2008 00:26:00 -0000 [thread overview] Message-ID: <bug-38281-12544@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1719 bytes --] Seen using r142231 on Ubuntu Hardy on x86. regehr@john-home:~/volatile/tmp69$ current-gcc -O small.c small.c: In function func_41: small.c:22: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. regehr@john-home:~/volatile/tmp69$ current-gcc -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../configure --program-prefix=current- --enable-languages=c,c++ --prefix=/home/regehr : (reconfigured) ../configure --program-prefix=current- --enable-languages=c,c++ --prefix=/home/regehr : (reconfigured) ../configure --program-prefix=current- --enable-languages=c,c++ --prefix=/home/regehr Thread model: posix gcc version 4.4.0 20081126 (experimental) (GCC) regehr@john-home:~/volatile/tmp69$ cat small.c typedef unsigned short int uint16_t; inline uint16_t safe_div_uint16_t_u_u (uint16_t ui1, uint16_t ui2) { if (ui2 == 0) return ui1; return ui1 / ui2; } uint16_t g_223; uint16_t g_243; int g_252; int func_41 (uint16_t p_42) { int l_258 = 0; int l_261 = 0x3D75D162L; g_223 = safe_div_uint16_t_u_u (g_243 > l_261, func_110 (l_258, 1)); for (g_252 = 0; g_252; g_252 = 1) { } } -- Summary: ice: Segmentation fault Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: regehr at cs dot utah dot edu GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38281
next reply other threads:[~2008-11-27 0:26 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-27 0:26 regehr at cs dot utah dot edu [this message] 2008-11-27 0:39 ` [Bug rtl-optimization/38281] " pinskia at gcc dot gnu dot org 2008-11-27 0:39 ` pinskia at gcc dot gnu dot org 2008-11-27 0:40 ` [Bug rtl-optimization/38281] [4.4 Regression] " pinskia at gcc dot gnu dot org 2008-11-27 1:02 ` pinskia at gcc dot gnu dot org 2008-11-27 10:03 ` jakub at gcc dot gnu dot org 2008-11-27 17:42 ` jsm28 at gcc dot gnu dot org 2008-11-29 2:46 ` pinskia at gcc dot gnu dot org 2008-12-03 8:43 ` ebotcazou at gcc dot gnu dot org 2008-12-03 8:49 ` [Bug rtl-optimization/38281] [4.4 Regression] segmentation fault with optimization enabled ebotcazou at gcc dot gnu dot 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-38281-12544@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).