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 target/37241] [4.4 Regression]: FAIL: g++.dg/abi/key2.C
Date: Wed, 22 Oct 2008 12:12:00 -0000	[thread overview]
Message-ID: <20081022121128.21334.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37241-12313@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from jakub at gcc dot gnu dot org  2008-10-22 12:11 -------
That sounds just too strict testcase matching, not expecting any kind of
reordering and .section directives not necessarily being emitted if an object
is emitted in the same section as the previous one.
FYI, on a x86_64-linux -> powerpc64-darwin cross, I see:
        .globl __ZTV1f
        .weak_definition __ZTV1f
        .section __TEXT,__const_coal,coalesced
...
        .globl __ZTI1f
        .weak_definition __ZTI1f
...
        .globl __ZTS1f
        .weak_definition __ZTS1f
(all in the same section and __TEXT used everywhere, not __DATA).


-- 


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


  parent reply	other threads:[~2008-10-22 12:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 11:52 [Bug target/37241] New: " dominiq at lps dot ens dot fr
2008-08-26 20:46 ` [Bug target/37241] " pinskia at gcc dot gnu dot org
2008-09-14  5:05 ` pinskia at gcc dot gnu dot org
2008-10-22  3:17 ` mmitchel at gcc dot gnu dot org
2008-10-22 12:12 ` jakub at gcc dot gnu dot org [this message]
2008-10-28 23:24 ` [Bug testsuite/37241] " pinskia at gcc dot gnu dot org
2008-10-28 23:34 ` jakub at gcc dot gnu dot org
2008-11-03 12:01 ` jakub at gcc dot gnu dot org
2008-11-03 12:01 ` jakub at gcc dot gnu dot org
2008-11-03 17:35 ` dominiq at lps dot ens dot fr
2008-11-03 20:28 ` jakub at gcc dot gnu dot org
2008-11-03 22:08 ` jakub at gcc dot gnu dot org
2008-11-03 22:10 ` 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=20081022121128.21334.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).