From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Tom Rini <trini@kernel.crashing.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Corey Minyard <minyard@acm.org>,
Franz Sirl <Franz.Sirl-ppc@lauterbach.com>,
linuxppc-dev@lists.linuxppc.org, paulus@samba.org
Subject: Re: Changes to PPC Linux required for GCC 3.1
Date: Wed, 5 Dec 2001 21:30:10 +0100 [thread overview]
Message-ID: <200112052124.4573@enzo.bigblue.local> (raw)
In-Reply-To: <20011205194522.GA28241@cpe-24-221-152-185.az.sprintbbd.net>
On Wednesday 05 December 2001 20:45, Tom Rini wrote:
> On Wed, Dec 05, 2001 at 06:50:38PM +0100, Benjamin Herrenschmidt wrote:
> > >I think the reason this wasn't applied is that Paul said something about
> > >thiws being horriyingly ugly. Corey, can you post a patch that changes
> > >RELOC(x) into a function and nothing else? :)
> >
> > I prefer this beeing resolved at compile time. The reason Paul didn't
> > want it at first is because he didn't want a workaround for a pre-release
> > gcc bug. Since this is becoming a "feature", it makes sense to get the
> > workaround. Paulus will confirm or not what I'm saying though...
>
> This was actually being hit by a 3.0.x release at the time I think (and
> we worked around it another way). I'd prefer a clean function over an
> ugly macro any day :)
I don't understand how my patch makes the RELOC hack uglier than it is
already by itself ;-). The few affected files should really be reworked to be
compiled with something like -fPIC -mrelocateable (maybe with -msdata and
setup r12 accordingly).
Franz.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-05 20:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 16:13 Changes to PPC Linux required for GCC 3.1 Corey Minyard
2001-12-04 16:16 ` David Edelsohn
2001-12-04 16:39 ` Corey Minyard
2001-12-05 12:55 ` Franz Sirl
2001-12-05 16:18 ` Corey Minyard
2001-12-05 17:37 ` Tom Rini
2001-12-05 17:50 ` Benjamin Herrenschmidt
2001-12-05 19:45 ` Tom Rini
2001-12-05 20:30 ` Franz Sirl [this message]
2001-12-07 13:01 ` Gabriel Paubert
2001-12-07 20:57 ` AltiVec register ptrace support Kumar Gala
2001-12-07 22:23 ` Kevin Buettner
2001-12-07 22:34 ` Daniel Jacobowitz
2001-12-14 18:52 ` Kumar Gala
2001-12-14 19:16 ` Jason R Thorpe
2001-12-15 2:08 ` Andrew Cagney
2001-12-15 17:44 ` Kumar Gala
2001-12-16 21:11 ` Paul Mackerras
2002-01-10 18:58 ` Kumar Gala
2001-12-05 21:59 ` Changes to PPC Linux required for GCC 3.1 Paul Mackerras
2001-12-05 20:17 ` Daniel Jacobowitz
2001-12-05 20:20 ` David Edelsohn
2001-12-05 20:30 ` Franz Sirl
2001-12-06 0:59 ` Corey Minyard
2001-12-06 3:38 ` Tom Rini
2001-12-07 5:22 ` Corey Minyard
2001-12-05 20:51 ` Franz Sirl
2001-12-06 1:41 ` Corey Minyard
-- strict thread matches above, loose matches on Subject: below --
2001-03-06 16:03 who loads argc in elf binary??????? Alexandre Nikolaev
2001-03-07 19:10 ` Daniel Jacobowitz
2001-03-07 19:15 ` David Edelsohn
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=200112052124.4573@enzo.bigblue.local \
--to=franz.sirl-kernel@lauterbach.com \
--cc=Franz.Sirl-ppc@lauterbach.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=minyard@acm.org \
--cc=paulus@samba.org \
--cc=trini@kernel.crashing.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 NNTP newsgroup(s).