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 other/52944] [4.5/4.6 Regression] __builtin_object_size(..., 1) no longer returns (size_t)-1 for consecutive flexible/zero-length array members
Date: Fri, 13 Apr 2012 09:31:00 -0000 [thread overview]
Message-ID: <bug-52944-4-dbMtOVtt3n@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52944-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52944
--- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-04-13 09:30:48 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
>
> wouldn't it though ? there's still a top level union there surrounding all the
> members. so flattening it, i'd get three choices:
> - th_block; th_data
> - th_code; th_data
> - th_stuff
>
> the problem before was that it was a union followed by th_data
>
> testing locally with gcc-4.6.2, i get the object sizes of:
> - -O0: th_data:-1 th_stuff:-1
> - -O[s123]: th_data:96 th_stuff:98
Ah, yeah. That might work reliably indeed. Though I find my solutions
nicer and more explicit ;)
prev parent reply other threads:[~2012-04-13 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 3:50 [Bug other/52944] New: " vapier at gentoo dot org
2012-04-12 9:21 ` [Bug other/52944] " rguenth at gcc dot gnu.org
2012-04-12 15:13 ` vapier at gentoo dot org
2012-04-12 15:28 ` rguenth at gcc dot gnu.org
2012-04-12 15:43 ` vapier at gentoo dot org
2012-04-13 9:31 ` rguenth at gcc dot gnu.org [this message]
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-52944-4-dbMtOVtt3n@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: link
Be 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).