Kaveh R. GHAZI - Re: [PATCH]: include GMP/MPFR version info in "gcc -v" output (original) (raw)

This is the mail archive of the gcc-patches@gcc.gnu.orgmailing list for the GCC project.

• From: "Kaveh R. GHAZI"
• To: Richard Guenther
• Cc: Gerald Pfeifer , gcc-patches at gcc dot gnu dot org
• Date: Sun, 18 Feb 2007 10:39:34 -0500 (EST)
• Subject: Re: [PATCH]: include GMP/MPFR version info in "gcc -v" output
• References: <Pine.GSO.4.58.0702171402110.1669@caipclassic.rutgers.edu> <Pine.LNX.4.64.0702172015310.16135@acrux.dbai.tuwien.ac.at> <Pine.GSO.4.58.0702171523520.1771@caipclassic.rutgers.edu> <84fc9c000702171236u19fb73d5kbdbb26678160bd16@mail.gmail.com> <Pine.GSO.4.58.0702171719380.1947@caipclassic.rutgers.edu> <84fc9c000702180129n3394420dg316f78678e272646@mail.gmail.com>

On Sun, 18 Feb 2007, Richard Guenther wrote:

I'm not sure I agree about combining the two. With the combined form, it's not clear to the user that gcc is checking internally that the two versions are identical. They may be left wondering whether gcc is showing the header or lib version or has the smarts to check both.

Well, "compiled by" implies this is a header (compile-time) check. Also I'm not sure anymore why we need gmp / mpfr version but not for example glibc version or binutils version as both are checked for features at gcc compile time as well (and there are known to be broken versions of those as well). Richard.

I don't think the glibc case is the same. The situation I'm coming across is that the user doesn't know which version of e.g. mpfr among two or several installed on their box that gcc is using. Having a way to show it helps debugging by them. I think it's more rare that users have more than more glibc installed and don't know which one they're linking with. If it turns out that case is common too, then we should add glibc, not block the gmp/mpfr displaying.

And actually we DO show the as/ld (i.e. binutils) version with gcc -v. I had been leaving it out of my sample output for brevity, but here it is for native tools on solaris. I assume it does the same on gnu-linux:

GNU C version 3.4.6 (sparc-sun-solaris2.10) compiled by GNU C version 3.4.6. GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 /usr/ccs/bin/as -V -Qy -s -xarch=v8 -o /var/tmp//ccLWyJLR.o /var/tmp//ccS5veBJ.s /usr/ccs/bin/as: Sun Compiler Common 10 Patch 05/06/2005 /caip/u12/kishgcc/tmpdisk/gcc-testing/basel34/build/gcc/collect2 -V -YP,/usr/ccs/lib:/usr/lib -Qy [...] ld: Software Generation Utilities - Solaris Link Editors: 5.10-1.482

So with that in mind, okay for mainline?

    Thanks,
    --Kaveh

-- Kaveh R. Ghazi ghazi@caip.rutgers.edu

• References:
  • [PATCH]: include GMP/MPFR version info in "gcc -v" output
    * From: Kaveh R. GHAZI
  • Re: [PATCH]: include GMP/MPFR version info in "gcc -v" output
    * From: Gerald Pfeifer
  • Re: [PATCH]: include GMP/MPFR version info in "gcc -v" output
    * From: Kaveh R. GHAZI
  • Re: [PATCH]: include GMP/MPFR version info in "gcc -v" output
    * From: Richard Guenther
  • Re: [PATCH]: include GMP/MPFR version info in "gcc -v" output
    * From: Kaveh R. GHAZI
  • Re: [PATCH]: include GMP/MPFR version info in "gcc -v" output
    * From: Richard Guenther