public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Gary Thomas <gdt@linuxppc.org>
Cc: Andreas Tobler <a.tobler@schweiz.ch>, egcs@egcs.cygnus.com
Subject: vtable thunks (was: RE: building egcs under LinuxPPC pre-R5)
Date: Wed, 10 Feb 1999 05:20:00 -0000	[thread overview]
Message-ID: <4.1.19990210133848.041dbf10@mail.lauterbach.com> (raw)
In-Reply-To: < XFMail.990210094035.gdt@linuxppc.org >

At 10:40 10.02.99 , Gary Thomas wrote:
>The latest snapshots are very unstable on Linux/PPC.  We are working on
>this now, but I'd stay away from them until further notice.
>
>On 10-Feb-99 Andreas Tobler wrote:
>> Hello,
>> 
>> since the beginning of February I try to build egcs snapshot 19990131
>> and now 19990208. The succcess is small. I got the 19990131 snapshot to
>> build and install, but when I compile c++ code with some include
>> restrictions it seems that it overrides it which causes an error. The
>> egcs I used before and now again, was 2.91.60 I think, for LinuxPPC
>> folks egcs-1.1.1.1c. With this compiler I haven't had this error.
>> My question, is there something specific when building an egcs on
>> LinuxPPC that I have to take care of? It's not necessary for me to take
>> a snapshot, but I need to build an egcs & libstdc++ with the option
>> -fno-vtable-thunks.
>
>The version of EGCS-1.1.1c that I uploaded should have been compiled this
>way.  What makes you think it was not?

He's probably talking about the pre-R5 egcs-1.1.1-1c RPM's which I prepared
for the R5 distribution. They have vtable-thunks enabled, as it is the
default for glibc-2.1 based egcs.
Gary, if you are producing RPM's for R5 which have vtable-thunks disabled,
I hope you are using versioning to distinguish the binary incompatible
libstdc++ stuff.

I would also appreciate if someone knowledgeable would document
(history/future, pros/cons, etc.) the whole vtable-thunks/no-vtable-thunks
stuff and put it in the FAQ.html (or a separate vtable.html?), cause
searching the mailinglists reveals 140 :-) documents on this issue.

Franz.

WARNING: multiple messages have this Message-ID
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Gary Thomas <gdt@linuxppc.org>
Cc: Andreas Tobler <a.tobler@schweiz.ch>, egcs@egcs.cygnus.com
Subject: vtable thunks (was: RE: building egcs under LinuxPPC pre-R5)
Date: Sun, 28 Feb 1999 22:53:00 -0000	[thread overview]
Message-ID: <4.1.19990210133848.041dbf10@mail.lauterbach.com> (raw)
Message-ID: <19990228225300.VE4rdrLmjHsTuT_gmYoRSqIO0A7XmIQe1-6ckxjIW80@z> (raw)
In-Reply-To: <XFMail.990210094035.gdt@linuxppc.org>

At 10:40 10.02.99 , Gary Thomas wrote:
>The latest snapshots are very unstable on Linux/PPC.  We are working on
>this now, but I'd stay away from them until further notice.
>
>On 10-Feb-99 Andreas Tobler wrote:
>> Hello,
>> 
>> since the beginning of February I try to build egcs snapshot 19990131
>> and now 19990208. The succcess is small. I got the 19990131 snapshot to
>> build and install, but when I compile c++ code with some include
>> restrictions it seems that it overrides it which causes an error. The
>> egcs I used before and now again, was 2.91.60 I think, for LinuxPPC
>> folks egcs-1.1.1.1c. With this compiler I haven't had this error.
>> My question, is there something specific when building an egcs on
>> LinuxPPC that I have to take care of? It's not necessary for me to take
>> a snapshot, but I need to build an egcs & libstdc++ with the option
>> -fno-vtable-thunks.
>
>The version of EGCS-1.1.1c that I uploaded should have been compiled this
>way.  What makes you think it was not?

He's probably talking about the pre-R5 egcs-1.1.1-1c RPM's which I prepared
for the R5 distribution. They have vtable-thunks enabled, as it is the
default for glibc-2.1 based egcs.
Gary, if you are producing RPM's for R5 which have vtable-thunks disabled,
I hope you are using versioning to distinguish the binary incompatible
libstdc++ stuff.

I would also appreciate if someone knowledgeable would document
(history/future, pros/cons, etc.) the whole vtable-thunks/no-vtable-thunks
stuff and put it in the FAQ.html (or a separate vtable.html?), cause
searching the mailinglists reveals 140 :-) documents on this issue.

Franz.


  parent reply	other threads:[~1999-02-10  5:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-10  0:34 building egcs under LinuxPPC pre-R5 Andreas Tobler
     [not found] ` < 36C144A0.A11501B1@schweiz.ch >
1999-02-10  1:40   ` Gary Thomas
     [not found]     ` < XFMail.990210094035.gdt@linuxppc.org >
1999-02-10  5:20       ` Franz Sirl [this message]
1999-02-10  5:32         ` vtable thunks (was: RE: building egcs under LinuxPPC pre-R5) Andreas
1999-02-28 22:53           ` Andreas
     [not found]         ` < 4.1.19990210133848.041dbf10@mail.lauterbach.com >
1999-02-10  5:39           ` Gary Thomas
1999-02-28 22:53             ` Gary Thomas
1999-02-28 22:53         ` Franz Sirl
1999-02-28 22:53     ` building egcs under LinuxPPC pre-R5 Gary Thomas
1999-02-28 22:53 ` Andreas Tobler

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=4.1.19990210133848.041dbf10@mail.lauterbach.com \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=a.tobler@schweiz.ch \
    --cc=egcs@egcs.cygnus.com \
    --cc=gdt@linuxppc.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).