From: Mark Mitchell <mark@codesourcery.com>
To: kthomas@gwdg.de
Cc: egcs@egcs.cygnus.com
Subject: Re: C++: STL 3.2
Date: Tue, 27 Apr 1999 13:18:00 -0000 [thread overview]
Message-ID: <199904272021.NAA14531@adsl-206-170-148-33.dsl.snfc21.pacbell.net> (raw)
In-Reply-To: <3726c80d.46773104@mailer.gwdg.de>
>>>>> "Philipp" == Philipp Thomas <kthomas@gwdg.de> writes:
Philipp> On Mon, 26 Apr 1999 12:04:22 -0700, you wrote:
>> We worked very hard to make these "sloppy" so that the kinds of
>> differences people don't care about didn't get flagged, unless
>> you were in a "pedantic" mode. Fun stuff, would be nice to
>> have in GCC someday.
Philipp> I agree that this sounds fun, but this task would be up
Philipp> to the binutils folks, no ?
Not entirely. You need cooperation both from the compiler and the
linker. (In our implementation, a separate prelinker was run, so we
only needed help from the compiler. In fact, we didn't even need that;
we just put stuff directly in the object-file after the compiler ran.)
But, in GNU-land, it would make sense to have the compiler insert the
ODR records and have the linker check them.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
WARNING: multiple messages have this Message-ID
From: Mark Mitchell <mark@codesourcery.com>
To: kthomas@gwdg.de
Cc: egcs@egcs.cygnus.com
Subject: Re: C++: STL 3.2
Date: Fri, 30 Apr 1999 23:15:00 -0000 [thread overview]
Message-ID: <199904272021.NAA14531@adsl-206-170-148-33.dsl.snfc21.pacbell.net> (raw)
Message-ID: <19990430231500.27vLf7YKDdvHHOX9UGTt1YKMrpGENakK8ATImSdKGQM@z> (raw)
In-Reply-To: <3726c80d.46773104@mailer.gwdg.de>
>>>>> "Philipp" == Philipp Thomas <kthomas@gwdg.de> writes:
Philipp> On Mon, 26 Apr 1999 12:04:22 -0700, you wrote:
>> We worked very hard to make these "sloppy" so that the kinds of
>> differences people don't care about didn't get flagged, unless
>> you were in a "pedantic" mode. Fun stuff, would be nice to
>> have in GCC someday.
Philipp> I agree that this sounds fun, but this task would be up
Philipp> to the binutils folks, no ?
Not entirely. You need cooperation both from the compiler and the
linker. (In our implementation, a separate prelinker was run, so we
only needed help from the compiler. In fact, we didn't even need that;
we just put stuff directly in the object-file after the compiler ran.)
But, in GNU-land, it would make sense to have the compiler insert the
ODR records and have the linker check them.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~1999-04-27 13:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-26 11:36 Mike Stump
1999-04-26 12:01 ` Mark Mitchell
1999-04-27 11:43 ` Philipp Thomas
1999-04-27 13:18 ` Mark Mitchell [this message]
1999-04-30 23:15 ` Mark Mitchell
1999-04-30 23:15 ` Philipp Thomas
1999-04-30 23:15 ` Mark Mitchell
[not found] ` <199904261904.MAA32332.cygnus.egcs@adsl-206-170-148-33.dsl.snfc21.pacbell.net>
1999-04-26 22:58 ` C++: STL 3.2 and egcs 1.2 Jason Merrill
1999-04-26 23:56 ` Mark Mitchell
1999-04-30 23:15 ` Mark Mitchell
1999-04-30 23:15 ` Jason Merrill
1999-04-30 23:15 ` C++: STL 3.2 Mike Stump
-- strict thread matches above, loose matches on Subject: below --
1999-04-23 7:44 Gerald Pfeifer
1999-04-24 22:28 ` Jeffrey A Law
1999-04-24 23:11 ` Mark Mitchell
1999-04-25 13:04 ` Martin v. Loewis
1999-04-30 23:15 ` Martin v. Loewis
1999-04-30 23:15 ` Mark Mitchell
1999-04-25 12:50 ` Martin v. Loewis
1999-04-25 14:46 ` Gabriel Dos_Reis
1999-04-30 23:15 ` Gabriel Dos_Reis
1999-04-30 23:15 ` Martin v. Loewis
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Gerald Pfeifer
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=199904272021.NAA14531@adsl-206-170-148-33.dsl.snfc21.pacbell.net \
--to=mark@codesourcery.com \
--cc=egcs@egcs.cygnus.com \
--cc=kthomas@gwdg.de \
/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).