From: willy@thepuffingroup.com
To: Sam Creasey <sammy@sammy.net>
Cc: Grant Grundler <grundler@cup.hp.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] crti.S Nested procedures error
Date: Wed, 3 May 2000 11:53:10 -0400 [thread overview]
Message-ID: <20000503115310.A27702@thepuffingroup.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0005031016340.6083-100000@sammyville.sammy.net>; from Sam Creasey on Wed, May 03, 2000 at 10:18:54AM -0400
On Wed, May 03, 2000 at 10:18:54AM -0400, Sam Creasey wrote:
> ok, for a while I was dealing with this by simply hacking up initfini.s by
> hand, but that wasn't necessary last time I built. I think this is
> related to the fact that somebody had taken out .proc/.procend from the
> assembler entirely (well, ignored them on ELF targets). I think this was
> a bad idea (if I remember tc-hppa.c from gas, it depends on these to build
> some of the global symbol information? It did something even on an elf
> target).
it was a bad idea, it broke other things. i suspect the right thing
to do is move some of the global symbol information-building code
which is currently invoked upon seeing a .proc or .procend to simply
seeing a non-local label, like the other assemblers do. i don't see why
linux/elf/pa-risc needs anything special in this regard. Alan (Modra),
do you have any comments?
> We might need our own magic sed script for parisc.
i'd prefer not to..
next prev parent reply other threads:[~2000-05-03 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-01 18:41 [parisc-linux] crti.S Nested procedures error Grant Grundler
2000-05-03 14:18 ` Sam Creasey
2000-05-03 15:53 ` willy [this message]
2000-05-04 0:28 ` Alan Modra
2000-05-10 20:03 ` Paul Bame
[not found] <200005040040.RAA14682@milano.cup.hp.com>
2000-05-04 0:49 ` Alan Modra
2000-05-04 0:54 ` Jeffrey A Law
2000-05-04 1:27 ` Alan Modra
2000-05-04 4:45 ` Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
2000-05-10 21:48 Cary Coutant
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=20000503115310.A27702@thepuffingroup.com \
--to=willy@thepuffingroup.com \
--cc=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=sammy@sammy.net \
/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