public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/36043] gcc reads 8 bytes for a struct of size 6 which leads to sigsegv Date: Mon, 28 Mar 2011 12:03:00 -0000 [thread overview] Message-ID: <bug-36043-4-GGY7E1DoI6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-36043-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36043 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|x86_64-unknown-linux-gnu |x86_64-unknown-linux-gnu, | |i?86-*-* Component|target |middle-end Known to fail| |2.95.2 --- Comment #16 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-03-28 11:57:36 UTC --- Also broken at least since GCC 2.95 on i?86 with struct colour { unsigned char red; unsigned char green; unsigned char blue; }; void print_colour(struct colour col) __attribute__((regparm(3))); void foo(struct colour *c) { print_colour(*c); }
next parent reply other threads:[~2011-03-28 11:58 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-36043-4@http.gcc.gnu.org/bugzilla/> 2011-03-28 12:03 ` rguenth at gcc dot gnu.org [this message] 2011-03-28 12:17 ` rguenth at gcc dot gnu.org 2012-02-02 15:08 ` bergner at gcc dot gnu.org 2012-02-02 15:47 ` bergner at gcc dot gnu.org 2014-02-22 21:09 ` david at fries dot net 2014-02-23 0:03 ` support@zzz-deskmobile.desk-mail.com 2014-02-25 19:45 ` arthur.j.odwyer at gmail dot com 2015-03-14 3:57 ` amodra at gmail dot com 2015-04-15 7:29 ` amodra at gcc dot gnu.org 2015-04-30 11:12 ` amodra at gcc dot gnu.org 2015-04-30 11:15 ` amodra at gmail dot com 2015-04-30 11:18 ` john.dallman at siemens dot com
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-36043-4-GGY7E1DoI6@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).