From: Joel Sherrill <joel@OARcorp.com>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: charlet@act-europe.fr, gcc@gcc.gnu.org
Subject: Re: gcc 3.4 - gnatmake has wrong gcc name
Date: Fri, 19 Mar 2004 17:07:00 -0000 [thread overview]
Message-ID: <405B1E1F.5030902@OARcorp.com> (raw)
In-Reply-To: <10403191314.AA23893@vlsi1.ultra.nyu.edu>
Richard Kenner wrote:
> I don't know. I believe it's ";version", e.g. GCC.EXE;2, but I'm no
> VMS expert.
>
> That's correct.
So if I modified the code to do something like this, would it
be OK algorithmically?
- strip off directory portion ("basename")
- do equivalent of "sed -e 's/;[0-9]$/''
- do equivalent of "sed -e 's/.[eE][Xx][eE]$//'
I still view this as not as robust as my patch
against 3.10p which used program_transform_name
and put more the real names in sdefault.adb.
--joel
next prev parent reply other threads:[~2004-03-19 16:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 14:52 Richard Kenner
2004-03-19 17:07 ` Joel Sherrill [this message]
2004-03-19 17:24 ` Arnaud Charlet
2004-03-19 21:30 ` Paul Koning
2004-03-19 18:28 ` Douglas B Rupp
-- strict thread matches above, loose matches on Subject: below --
2004-03-19 14:18 Richard Kenner
2004-03-17 15:43 Joel Sherrill
2004-03-18 9:11 ` Jim Wilson
2004-03-18 9:37 ` Arnaud Charlet
2004-03-18 14:24 ` Joel Sherrill
2004-03-18 20:07 ` Jim Wilson
2004-03-18 23:58 ` Joel Sherrill
2004-03-19 11:19 ` Arnaud Charlet
2004-03-19 12:31 ` Jim Wilson
2004-03-19 13:06 ` Arnaud Charlet
2004-03-19 14:14 ` Joel Sherrill
2004-03-19 13:53 ` Joel Sherrill
2004-03-19 14:45 ` Arnaud Charlet
2004-03-19 19:59 ` Gabriel Paubert
2004-03-20 23:08 ` Joel Sherrill
2004-03-20 23:58 ` Paul Koning
2004-03-21 18:03 ` Joel Sherrill
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=405B1E1F.5030902@OARcorp.com \
--to=joel@oarcorp.com \
--cc=charlet@act-europe.fr \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).