public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc-bugzilla at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/14542] New: ICE on simple source Date: Fri, 12 Mar 2004 01:56:00 -0000 [thread overview] Message-ID: <20040312015624.14542.namsh@kldp.org> (raw) Here is is ICE message: $ m6811-elf-gcc -c -m68hc12 -O3 -fomit-frame-pointer strcat.c strcat.c: In function `strcat': strcat.c:18: internal compiler error: in verify_local_live_at_start, at flow.c:546 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. Environment: System: Linux namsh 2.6.4 #66 Thu Mar 11 22:55:35 KST 2004 i686 athlon i386 GNU/Linux Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: m6811-unknown-none configured with: ../configure --disable-nls --target=m6811-elf --prefix=/usr/GNUHCS --program-prefix=m6811-elf- --with-gnu-ld --with-gnu-as --disable-shared --enable-languages=c,c++ --without-headers --with-newlib How-To-Repeat: Here is a source: /* strcat.c */ char *strcat(char *d, const char *s) { char *p = d; while (*d) d++; while ((*d = *s) != '\0') { d++; s++; } return p; } ------- Additional Comments From namsh at kldp dot org 2004-03-12 01:56 ------- Fix: 1. Do not use '-fomit-frame-pointer' 2. Use '-O2' instead of '-O3'. -- Summary: ICE on simple source Product: gcc Version: 3.4 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: namsh at kldp dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: m6811-unknown-none http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14542
next reply other threads:[~2004-03-12 1:56 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-12 1:56 gcc-bugzilla at gcc dot gnu dot org [this message] 2004-03-12 4:53 ` [Bug target/14542] " pinskia at gcc dot gnu dot org 2004-03-19 6:45 ` pinskia at gcc dot gnu dot org 2004-03-19 6:45 ` kazu at cs dot umass dot edu 2004-06-06 9:48 ` ciceron at gcc dot gnu dot org 2004-06-06 16:56 ` cvs-commit at gcc dot gnu dot org 2004-06-06 17:01 ` cvs-commit at gcc dot gnu dot org 2004-06-06 17:03 ` ciceron at gcc dot gnu dot org 2004-06-06 18:35 ` pinskia 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=20040312015624.14542.namsh@kldp.org \ --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).