public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/21860] New: Frontends should be adding DECL_EXPRs for TYPE_DECLs, at least when the type has SAVE_EXPRs in it
Date: Wed, 01 Jun 2005 10:21:00 -0000	[thread overview]
Message-ID: <20050601102126.21860.jakub@gcc.gnu.org> (raw)

See http://gcc.gnu.org/ml/gcc-patches/2005-05/msg02644.html
 > ... or the frontends would need to guarantee that for all types with some
 > variable TYPE_SIZE reachable from the type there would be a DECL_EXPR with
 > TYPE_DECL right before the first use of such type.
 > What's your preference?

 This later option should be the eventual goal.  That's not appropriate
 for the 4.0 branch though.  Your posted patch plus some additions for
 aggregates should be good enough for that.

-- 
           Summary: Frontends should be adding DECL_EXPRs for TYPE_DECLs, at
                    least when the type has SAVE_EXPRs in it
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jakub at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2005-06-01 10:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 10:21 jakub at gcc dot gnu dot org [this message]
2005-06-19 14:05 ` [Bug c/21860] " pinskia at gcc dot gnu dot org
2005-09-18  1:57 ` pinskia 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=20050601102126.21860.jakub@gcc.gnu.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).