public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/19515] [4.0 Regression] Violation of C99 6.7.8 §21 for unions
Date: Thu, 20 Jan 2005 11:28:00 -0000	[thread overview]
Message-ID: <20050120112836.5180.qmail@sourceware.org> (raw)
In-Reply-To: <20050118221058.19515.ebotcazou@gcc.gnu.org>


------- Additional Comments From rth at gcc dot gnu dot org  2005-01-20 11:28 -------
(In reply to comment #7)
> So we cannot use count_type_elements in gimplify_init_constructor. 

Well, not for unions anyway.

> I think we should somehow compute the size of the CONSTRUCTOR and compare 
> it with int_size_in_bytes (TREE_TYPE (object))...? 

For unions, that may be what we have to do.  With any luck, the element
being initialized will be the largest element of the union, which would
mean we wouldn't have to emit the clear.

For structures, this would mean that any structure with holes would get
cleared.  Which would clearly pessimize a very common case.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19515


  parent reply	other threads:[~2005-01-20 11:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-18 22:11 [Bug c/19515] New: [4.0 Regression] Violation of C99 6.7.8 §21 ebotcazou at gcc dot gnu dot org
2005-01-18 23:06 ` [Bug middle-end/19515] " pinskia at gcc dot gnu dot org
2005-01-18 23:12 ` ebotcazou at gcc dot gnu dot org
2005-01-18 23:23 ` pinskia at gcc dot gnu dot org
2005-01-18 23:37 ` steven at gcc dot gnu dot org
2005-01-19  0:08 ` pinskia at gcc dot gnu dot org
2005-01-20  9:04 ` steven at gcc dot gnu dot org
2005-01-20  9:11 ` steven at gcc dot gnu dot org
2005-01-20  9:16 ` [Bug middle-end/19515] [4.0 Regression] Violation of C99 6.7.8 §21 for unions ebotcazou at gcc dot gnu dot org
2005-01-20  9:26 ` stevenb at suse dot de
2005-01-20  9:31 ` ebotcazou at gcc dot gnu dot org
2005-01-20 11:28 ` rth at gcc dot gnu dot org [this message]
2005-01-20 11:49 ` steven at gcc dot gnu dot org
2005-01-20 18:03 ` rth at gcc dot gnu dot org
2005-01-26 15:21 ` cvs-commit at gcc dot gnu dot org
2005-01-26 15:25 ` rth 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=20050120112836.5180.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: 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).