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 debug/36668] [4.4 Regression] FAIL: g++.dg/other/PR23205.C scan-assembler .stabs.*foobar:c=i
Date: Tue, 21 Oct 2008 11:47:00 -0000	[thread overview]
Message-ID: <20081021114607.21360.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36668-276@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from jakub at gcc dot gnu dot org  2008-10-21 11:46 -------
With -fno-toplevel-reorder this generated foobar variable in .rodata already in
4.3, maybe earlier.  The interesting code is in decide_is_variable_needed:
  /* When not reordering top level variables, we have to assume that
     we are going to keep everything.  */
  if (flag_toplevel_reorder)
    return false;

  /* We want to emit COMDAT variables only when absolutely necessary.  */
  if (DECL_COMDAT (decl))
    return false;
  return true;
Is that true even with unit-at-a-time that we have to assume all vars are
potentially used?  After all, we should know all the variables, their
initializers and functions at this point.

If we can't change this, then I guess either the testcase should be passed
-ftoplevel-reorder, or matching foobar:(c=i|S) .  Honza?


-- 


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


  parent reply	other threads:[~2008-10-21 11:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-29 16:18 [Bug debug/36668] New: " danglin at gcc dot gnu dot org
2008-06-30 11:37 ` [Bug debug/36668] [4.4 Regression] " rguenth at gcc dot gnu dot org
2008-07-18 16:56 ` rguenth at gcc dot gnu dot org
2008-07-20 12:37 ` hp at gcc dot gnu dot org
2008-10-21 11:47 ` jakub at gcc dot gnu dot org [this message]
2008-10-21 16:15 ` rguenth at gcc dot gnu dot org
2008-10-29 19:14 ` jakub at gcc dot gnu dot org
2008-10-30  0:11 ` jakub at gcc dot gnu dot org
2008-10-30  0:49 ` jakub 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=20081021114607.21360.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).