public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: preprocessor/6084: cpp Segmentation Fault
Date: Fri, 12 Apr 2002 13:36:00 -0000	[thread overview]
Message-ID: <20020412203600.28226.qmail@sources.redhat.com> (raw)

The following reply was made to PR preprocessor/6084; it has been noted by GNATS.

From: Phil Edwards <phil@jaj.com>
To: joshg@hf.intel.com, gcc-gnats@gcc.gnu.org, rnesius@ichips.intel.com,
   tuan.nguyen@intel.com, gcc-bugs@gcc.gnu.org, neil@daikokuya.demon.co.uk
Cc:  
Subject: Re: preprocessor/6084: cpp Segmentation Fault
Date: Fri, 12 Apr 2002 16:27:07 -0400

 I haven't been able to reproduce this using today's 3.1 sources.  (More at
 the end.)
 
 55% cat 6084_hello.c
 #include <stdio.h>
 #ifdef MATHTEST
 #include <math.h>
 #endif
 
 main()
 {
  float X;
  printf("Hello, World! \n");
  #ifdef MATHTEST
  X = sqrt(4);
  printf("the sqrt of 4 is %f \n", X);
  #endif
 }
 
 56% gcc -DPERL_CORE -fno-strict-aliasing -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -mcpu=v9 -m64 -Wa,-xarch=v9 -O3 -m64 -dM -dD -dI -v 6084_hello.c
 Reading specs from /local/pme/instdir-v9/lib/gcc-lib/sparcv9-sun-solaris2.8/3.1/specs
 Configured with: /local/pme/unified/configure --prefix=/local/pme/instdir-v9 --enable-languages=c sparcv9-sun-solaris2.8
 Thread model: posix
 gcc version 3.1 20020412 (prerelease)
  /local/pme/instdir-v9/lib/gcc-lib/sparcv9-sun-solaris2.8/3.1/cc1 -lang-c -v -D__GNUC__=3 -D__GNUC_MINOR__=1 -D__GNUC_PATCHLEVEL__=0 -Dsparc -Dsun -Dunix -D__svr4__ -D__SVR4 -D__PRAGMA_REDEFINE_EXTNAME -D__sparc__ -D__sun__ -D__unix__ -D__svr4__ -D__SVR4 -D__PRAGMA_REDEFINE_EXTNAME -D__sparc -D__sun -D__unix -Asystem=unix -Asystem=svr4 -D__OPTIMIZE__ -D__STDC_HOSTED__=1 -D__SIZE_TYPE__=long unsigned int -D__PTRDIFF_TYPE__=long int -D__WCHAR_TYPE__=int -D__WINT_TYPE__=int -D__arch64__ -Acpu=sparc64 -Amachin e=sparcv9 -D__sparcv9 -DPERL_CORE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 6084_hello.c -quiet -dumpbase 6084_hello.c -dM -dD -dI -mcpu=v9 -m64 -m64 -O3 -version -fno-strict-aliasing -o /tmp/pedwards/ccGyKzGh.s
 GNU CPP version 3.1 20020412 (prerelease) (cpplib) (sparc ELF)
 GNU C version 3.1 20020412 (prerelease) (sparcv9-sun-solaris2.8)
         compiled by GNU C version 3.1 20020412 (prerelease).
 ignoring nonexistent directory "/local/pme/instdir-v9/sparcv9-sun-solaris2.8/include"
 #include "..." search starts here:
 #include <...> search starts here:
  /usr/local/include
  /local/pme/instdir-v9/include
  /local/pme/instdir-v9/lib/gcc-lib/sparcv9-sun-solaris2.8/3.1/include
  /usr/include
 End of search list.
  /usr/ccs/bin/as -V -Qy -s -xarch=v9 -xarch=v9 -o /tmp/pedwards/ccLEQgFp.o /tmp/pedwards/ccGyKzGh.s
 /usr/ccs/bin/as: Sun WorkShop 6 99/08/18
  /local/pme/instdir-v9/lib/gcc-lib/sparcv9-sun-solaris2.8/3.1/collect2 -V -Y P,/usr/lib/sparcv9 -Qy /local/pme/instdir-v9/lib/gcc-lib/sparcv9-sun-solaris2.8/3.1/crt1.o /local/pme/instdir-v9/lib/gcc-lib/sparcv9-sun-solaris2.8/3.1/crti.o /usr/lib/sparcv9/values-Xa.o /local/pme/instdir-v9/lib/gcc-lib/sparcv9-sun-solaris2.8/3.1/crtbegin.o -L/local/pme/instdir-v9/lib/gcc-lib/sparcv9-sun-solaris2.8/3.1 -L/usr/ccs/bin -L/usr/ccs/lib -L/local/pme/instdir-v9/lib/gcc-lib/sparcv9-sun-solaris2.8/3.1/../../.. /tmp/pedw ards/ccLEQgFp.o -lgcc -lgcc_eh -lc -lgcc -lgcc_eh -lc /local/pme/instdir-v9/lib/gcc-lib/sparcv9-sun-solaris2.8/3.1/crtend.o /local/pme/instdir-v9/lib/gcc-lib/sparcv9-sun-solaris2.8/3.1/crtn.o
 ld: Software Generation Utilities - Solaris-ELF (4.0)
 57%
 
 
 A few observations that probably make no difference to this PR:
 
 - I note that you configured your compiler for "sparcv9-sun-solaris2".
   Usually the final bit is a complete OS version, like 2.7 or 2.8.
 
 - Your system was reported as
     SunOS 5.7 Generic_106541-19 sun4u sparc SUNW,Ultra-2
   The one I used to test is
     SunOS 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-30
 
 - You mentioned you were using NFS and AFS.  My test was all local.
 
 
 Phil
 
 -- 
 If ye love wealth greater than liberty, the tranquility of servitude greater
 than the animating contest for freedom, go home and leave us in peace.  We seek
 not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
 and may posterity forget that ye were our countrymen.            - Samuel Adams


             reply	other threads:[~2002-04-12 20:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12 13:36 Phil Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-21 13:34 neil
2002-05-21 13:33 neil
2002-04-17 23:52 neil
2002-04-15 19:46 Gerwin, Joshua A
2002-04-15 18:06 Richard Henderson
2002-04-15 12:06 'Neil Booth'
2002-04-15 11:36 Gerwin, Joshua A
2002-04-15 11:16 'Neil Booth'
2002-04-15 11:06 Gerwin, Joshua A
2002-04-13  1:26 Phil Edwards
2002-04-13  1:16 Phil Edwards
2002-04-12 22:16 Neil Booth
2002-04-12 16:06 Gerwin, Joshua A
2002-04-03 22:36 'Neil Booth'
2002-04-03 17:06 Gerwin, Joshua A
2002-04-02 22:36 Neil Booth
2002-03-29 12:16 Neil Booth
2002-03-29 11:36 Gerwin, Joshua A
2002-03-29  0:20 neil

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=20020412203600.28226.qmail@sources.redhat.com \
    --to=phil@jaj.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).