Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: brobecker@gnat.com, gdb-patches@sources.redhat.com
Subject: Re: more robust get_compiler_info
Date: Fri, 06 Feb 2004 18:33:00 -0000	[thread overview]
Message-ID: <4023DDF0.4030403@gnu.org> (raw)
In-Reply-To: <20040205231351.9529A4B364@berman.michael-chastain.com>

> ac> ... can instead just compiler_info be set. 
> 
> Sounds good to me.  I will give it a whirl.
> 
> Here is the new patch, not tested yet, not even a ChangeLog entry.
> 
> Michael C
> 
> ===
> 
> Index: lib/compiler.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/lib/compiler.c,v
> retrieving revision 1.3
> diff -c -3 -p -r1.3 compiler.c
> *** lib/compiler.c	24 Jan 2004 21:59:03 -0000	1.3
> --- lib/compiler.c	5 Feb 2004 23:11:00 -0000
> ***************
> *** 34,60 ****
>   
>      TODO: purge signed_keyword_not_used.  */
>   
> ! set compiler_info ""
>   
>   #if defined (__GNUC__)
>   set compiler_info [join {gcc __GNUC__ __GNUC_MINOR__ } -]
> - set gcc_compiled __GNUC__
> - #else
> - set gcc_compiled 0
>   #endif
>   
>   #if defined (__HP_cc)
>   set compiler_info [join {hpcc __HP_cc} -]
> - set hp_cc_compiler __HP_cc
> - #else
> - set hp_cc_compiler 0
>   #endif
>   
>   #if defined (__HP_aCC)
>   set compiler_info [join {hpacc __HP_aCC} -]
> - set hp_aCC_compiler __HP_aCC
> - #else
> - set hp_aCC_compiler 0
>   #endif

Already like it :-)

Andrew



  reply	other threads:[~2004-02-06 18:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 23:13 Michael Elizabeth Chastain
2004-02-06 18:33 ` Andrew Cagney [this message]
2004-02-07  3:02 ` Joel Brobecker
  -- strict thread matches above, loose matches on Subject: below --
2004-02-05 22:53 Michael Elizabeth Chastain
2004-02-05 12:34 Michael Elizabeth Chastain
2004-02-05 15:03 ` Daniel Jacobowitz
2004-02-05 15:26 ` Andrew Cagney

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=4023DDF0.4030403@gnu.org \
    --to=cagney@gnu.org \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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