From: Momchil Velikov <velco@fadata.bg>
To: Jason R Thorpe <thorpej@wasabisystems.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] [RFC] NetBSD note segment
Date: Sun, 03 Nov 2002 10:13:00 -0000 [thread overview]
Message-ID: <20021103200916.3d434738.velco@fadata.bg> (raw)
In-Reply-To: <20021103095724.U29066@dhcp7.wlan.shagadelic.org>
On Sun, 3 Nov 2002 09:57:24 -0800
Jason R Thorpe <thorpej@wasabisystems.com> wrote:
> On Sun, Nov 03, 2002 at 07:45:55PM +0200, Momchil Velikov wrote:
>
> > How about putting them in the compiler's crtbegin/crtend files?
> > That would require changing only gcc/config/netbsd.h and
> > gcc/crtstuff.c instead of changing crt{i|n} of all the NetBSD CPUs
> > (which seem quite a large number :)
>
> Err, I already said that the compiler-supplied files should not supply
> the notes.
But crti/crtn are compiler supplied, too ?
~velco
next prev parent reply other threads:[~2002-11-03 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-03 3:20 Momchil Velikov
2002-11-03 8:10 ` Jason R Thorpe
2002-11-03 9:22 ` Momchil Velikov
2002-11-03 9:25 ` Jason R Thorpe
2002-11-03 9:50 ` Momchil Velikov
2002-11-03 9:57 ` Jason R Thorpe
2002-11-03 10:13 ` Momchil Velikov [this message]
2002-11-03 10:20 ` Jason R Thorpe
2002-11-03 9:14 ` Momchil Velikov
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=20021103200916.3d434738.velco@fadata.bg \
--to=velco@fadata.bg \
--cc=gcc-patches@gcc.gnu.org \
--cc=thorpej@wasabisystems.com \
/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).