public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/17053] New: [3.5 Regression] Repo functionality partially broken on AIX
Date: Mon, 16 Aug 2004 21:47:00 -0000	[thread overview]
Message-ID: <20040816214702.17053.dje@gcc.gnu.org> (raw)

Mark Mitchell's patch to clean up linkage handling has damaged -frepo
functionality on AIX and has caused a number of regressions in the testsuite:

g++.old-deja/g++.pt/instantiate4.C
g++.old-deja/g++.pt/instantiate6.C
g++.old-deja/g++.pt/repo1.C
g++.old-deja/g++.pt/repo2.C
g++.old-deja/g++.pt/repo4.C

The testcases now all result in a linker error.

./xgcc -B./ -c -frepo repo4.C
./xgcc -B./ -frepo repo4.o
collect: recompiling repo4.C
collect: relinking
ld: 0711-317 ERROR: Undefined symbol: _GLOBAL__F_main

After the linkage patch, the existence of frame info for some functions depends
on whether the -frepo option is present.  collect2.c does not re-scan the object
file as part of relinking and uses the existing frame information from the first
scan referencing frame info that no longer is present when relinking without
-frepo option.

I have tracked down the difference in frame info to the call to _ZN1SIiED1Ev. 
Depending on the presence of -frepo, the tree for that call gets marked
TREE_NOTHROW, causing ecf_flags to have ECF_NOTHROW set, causing REG_EH_REGION
reg_note to be attached to the RTL, causing the TREE_NOTHROW and
all_throwers_are_sibcalls to be cleared for the function, causing
output_call_frame_info() to determine that no unwinding will be needed and not
emitting any frame info.

For targets that do not use collect2, the change in frame info probably will go
unnoticed.  I do not know if the new -frepo-dependent behavior is intentional
and/or a consequence of the lazy evaluation.

I am not sure whether the NOTHROW property should be changing.  collect2
possibly could be changed to rescan the files when relinking, but that may be
papering over a problem if NOTHROW should be consistent.

-- 
           Summary: [3.5 Regression] Repo functionality partially broken on
                    AIX
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dje at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: powerpc-ibm-aix5.1.0.0
  GCC host triplet: powerpc-ibm-aix5.1.0.0
GCC target triplet: powerpc-ibm-aix5.1.0.0


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


             reply	other threads:[~2004-08-16 21:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16 21:47 dje at gcc dot gnu dot org [this message]
2004-08-16 21:50 ` [Bug c++/17053] " pinskia at gcc dot gnu dot org
2004-08-17  1:49 ` dje at gcc dot gnu dot org
2004-08-17  3:35 ` mmitchel at gcc dot gnu dot org
2004-08-17  3:37 ` mmitchel at gcc dot gnu dot org
2004-08-17  5:50 ` mmitchel at gcc dot gnu dot org
2004-08-17  5:53 ` pinskia at gcc dot gnu dot org
2004-08-17 15:08 ` dje at gcc dot gnu dot org
2004-08-17 15:49 ` mark at codesourcery dot com
2004-08-17 15:56 ` dje at watson dot ibm dot com
2004-08-17 16:01 ` mark at codesourcery dot com
2004-10-14 14:49 ` [Bug c++/17053] [4.0 " dje at gcc dot gnu dot org
2004-11-26 23:28 ` [Bug c++/17053] [4.0 Regression] Repo functionality partially broken on AIX (collect2.c) neroden at gcc dot gnu dot org
2005-03-24 19:58 ` [Bug c++/17053] [4.0/4.1 " dje at gcc dot gnu dot org
2005-04-17  3:01 ` mmitchel at gcc dot gnu dot org
2005-07-06 16:45 ` mmitchel at gcc dot gnu dot org
2005-09-27 16:17 ` mmitchel 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=20040816214702.17053.dje@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).