public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meklund at cisco dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/44386] builtin_object_size_ assumes a flexible array for a long array in a structure of known length Date: Wed, 02 Jun 2010 16:33:00 -0000 [thread overview] Message-ID: <20100602163325.9890.qmail@sourceware.org> (raw) In-Reply-To: <bug-44386-11981@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from meklund at cisco dot com 2010-06-02 16:33 ------- I've re-run the code varying the flag from 0 to 3 (instead of hard coding to 3) with the below results. The unexpected results are still happening for 'a', 'b', 'd', and 'f'. a b c d e f 0: -1 200 -1 -1 200 160 1: -1 200 40 -1 40 160 2: 0 200 0 0 200 160 3: 0 200 40 0 40 160 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44386
next prev parent reply other threads:[~2010-06-02 16:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-02 15:15 [Bug c/44386] New: " meklund at cisco dot com 2010-06-02 16:33 ` meklund at cisco dot com [this message] 2010-06-02 18:04 ` [Bug middle-end/44386] " pinskia at gcc dot gnu dot org 2010-06-02 18:05 ` [Bug c/44386] " jakub at gcc dot gnu dot org 2010-06-07 15:27 ` [Bug middle-end/44386] " meklund at cisco 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=20100602163325.9890.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).