From: Paul Gilliam <pgilliam@us.ibm.com>
To: gdb-patches@sources.redhat.com
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: [patch] seperate HP aCC compiler_info into Major, Minor, and Extension
Date: Fri, 15 Apr 2005 19:35:00 -0000 [thread overview]
Message-ID: <200504151234.14115.pgilliam@us.ibm.com> (raw)
In-Reply-To: <20050414191631.GF26377@nevyn.them.org>
On Thursday 14 April 2005 12:16, Daniel Jacobowitz wrote:
> On Fri, Apr 08, 2005 at 02:21:07PM -0800, Paul Gilliam wrote:
> > This patch seperates the compiler info string for the HP aCC compiler into it's components.
> > The old value for version A.01.21 was hpacc-010121; the new value would be hpacc-01-01-21.
> > This is consistant with the why GCC is handled.
> >
> > -=# Paul #=-
> >
> > ---
> > 2005-04-08 Paul Gilliam <pgilliam@us.ibm.com>
> >
> > * lib/compiler.c: Divide HP aCC 'compiler_info' into components.
> > * lib/compiler.cc: Likewise.
>
> Not OK I'm afraid. I tried an aCC installation I had handy:
>
> bash-2.05b$ aCC --version
> aCC: HP ANSI C++ B3910B A.03.45
>
> set compiler_info [join {hpacc 34500 } -]
>
> That's not going to match your regexp.
>
From the doc I read on the net somewhere, that version info
should be translated into 'hpacc 010345'.
And we all know, the net nevers is wrong. 8-(
should it be changed to:
set need_a_set [eval {regexp {1(..)(..)(..)} [expr __HP_aCC + 1000000] dontcare nn xx mm;set compiler_info "hpacc-$mm-$nn-$xx"}]
or to:
set need_a_set [eval {regexp {1(..)(..)(..)..} [expr __HP_aCC + 100000000] dontcare mm nn xx;set compiler_info "hpacc-$mm-$nn-$xx"}]
or just forget the whole thing? Maybe this is more futzing around than it's worth.
(But I do like it when things are consistant.)
-=# Paul #=-
next prev parent reply other threads:[~2005-04-15 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 22:23 Paul Gilliam
2005-04-14 19:16 ` Daniel Jacobowitz
2005-04-15 19:35 ` Paul Gilliam [this message]
2005-04-15 19:36 ` Daniel Jacobowitz
2005-04-15 19:42 ` Paul Gilliam
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=200504151234.14115.pgilliam@us.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.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