public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/42528] ICE with -flto and -fsigned-char Date: Sun, 03 Jan 2010 17:31:00 -0000 [thread overview] Message-ID: <20100103173104.19621.qmail@sourceware.org> (raw) In-Reply-To: <bug-42528-8090@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from rguenth at gcc dot gnu dot org 2010-01-03 17:31 ------- The same problem exists for builtin functions that return or take arguments of type char *. They change signature according to -f[un]signed-char which causes for example FAIL: gcc.c-torture/execute/builtins/strcpy-chk.c compilation, -O2 -flto (internal compiler error) when running with -funsigned-char on x86: char p[32] = ""; int main () { if (__builtin___strcpy_chk (p + 1, "vwxyz", __builtin_object_size (p + 1, 0)) != p + 1) __builtin_abort (); return 0; } $ /obj/trunk-g/gcc/xgcc -B/obj/trunk-g/gcc/ strcpy-chk.3.i -O -flto -funsigned-char In file included from :0:0: strcpy-chk.3.i: In function 'main': strcpy-chk.3.i:2:5: error: non-trivial conversion at assignment <unnamed-unsigned:8> * <unnamed-signed:8> * D.2023_3 = D.2027_5; strcpy-chk.3.i:2:5: internal compiler error: verify_stmts failed Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42528
next prev parent reply other threads:[~2010-01-03 17:31 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-28 22:58 [Bug lto/42528] New: " anton at samba dot org 2009-12-31 15:09 ` [Bug lto/42528] " rguenth at gcc dot gnu dot org 2010-01-03 14:33 ` rguenth at gcc dot gnu dot org 2010-01-03 17:31 ` rguenth at gcc dot gnu dot org [this message] 2010-01-03 18:12 ` rguenth at gcc dot gnu dot org 2010-01-03 18:21 ` rguenth at gcc dot gnu dot org 2010-01-07 11:01 ` anton at samba dot org 2010-01-08 16:58 ` rguenth at gcc dot gnu dot org 2010-01-08 16:58 ` rguenth 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=20100103173104.19621.qmail@sourceware.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).