public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Richard B. Kreckel" <kreckel@ginac.de>
To: ro@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/5505: Doubts about a patch for OSF
Date: Wed, 20 Feb 2002 09:36:00 -0000	[thread overview]
Message-ID: <20020220172600.20558.qmail@sources.redhat.com> (raw)

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

From: "Richard B. Kreckel" <kreckel@ginac.de>
To: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: target/5505: Doubts about a patch for OSF
Date: Wed, 20 Feb 2002 18:16:41 +0100 (CET)

 Hi,
 
 On Tue, 19 Feb 2002, Rainer Orth wrote:
 [...]
 > two things: please provide g++ -v output for some individual compilation of
 > CLN, so I can see exactly how gcc was configured.
 > 
 > Besides, could you run one of the crashing programs (tests/tests or
 > tests/exam, I suppose) under ladebug to get at least an idea where it
 > crashes?  While older versions of ladebug simply bail out on gcc compiled
 > code with stabs-in-ECOFF debugging information, recent versions recognize
 > and ignore it, but should get you a stack trace.  If this leads nowhere,
 > we might be able to get some further debugging done with a copy of gdb 5.0
 > hacked up to somewhat work on 5.1.
 
 Err, while trying to debug into the problem I discovered something
 that had escaped my attantion until now: compiling CLN and an example
 (examples/e, or tests/tests or whatever, never mind) with either -O1, -O2
 or -O1 -g resulted in a working test (the linker warnings are of course
 still present) while -O2 -fno-exceptions produced a crashing program.
 Also, these funny warnings:
  as1: Warning: /tmp/ccb8ZbYD.s, line 6: macro instruction used $at
 appear only when I disable exceptions.  I hadn't noticed it so far because
 I *always* export CXXFLAGS="-O2 -fno-exceptions" prior to building
 CLN.  May I ask you how you configured and tested CLN?  You did not
 specify -fno-exceptions, did you?  Does it work when you do so?
 
 Anyways, here is a g++ -v output as you requested:
 
 micky:~/src/patch358/cln-1.1.4/src$ g++ -v -O -I/homes/iphuthep/kreckel/DUX4/include -I../include -I./integer -I./base/digitseq -I./base/digit -Ibase -I./base -c ./integer/ring/cl_0_ring.cc -o cl_0_ring.o
 Reading specs from /homes/iphuthep/kreckel/DUX4/lib/gcc-lib/alphaev67-dec-osf5.1/3.0.3/specs
 Configured with: ../gcc-3.0.3/configure --prefix=/homes/iphuthep/kreckel/DUX4
 Thread model: single
 gcc version 3.0.3
  /homes/iphuthep/kreckel/DUX4/lib/gcc-lib/alphaev67-dec-osf5.1/3.0.3/cc1plus -v -I/homes/iphuthep/kreckel/DUX4/include -I../include -I./integer -I./base/digitseq -I./base/digit -Ibase -I./base -D__GNUC__=3 -D__GNUC_MINOR__=0 -D__GNUC_PATCHLEVEL__=3 -Dunix -D__osf__ -D_LONGLONG -DSYSTYPE_BSD -D_SYSTYPE_BSD -D__unix__ -D__osf__ -D_LONGLONG -D__SYSTYPE_BSD__ -D_SYSTYPE_BSD -D__unix -D__SYSTYPE_BSD -Asystem=unix -Asystem=xpg4 -D__OPTIMIZE__ -D__STDC_HOSTED__=1 -D__LANGUAGE_C_PLUS_PLUS__ -D__LANGUAGE_C_PLUS_PLU S -D__cplusplus -Acpu=alpha -Amachine=alpha -D__alpha -D__alpha__ -D__alpha_ev6__ -Acpu=ev6 -D__alpha_bwx__ -Acpu=bwx -D__alpha_max__ -Acpu=max -D__alpha_fix__ -Acpu=fix -D__alpha_cix__ -Acpu=cix -D__X_FLOAT ./integer/ring/cl_0_ring.cc -D__GNUG__=3 -D__GXX_DEPRECATED -D__EXCEPTIONS -D__GXX_ABI_VERSION=100 -quiet -dumpbase cl_0_ring.cc -O -version -o /tmp/ccHKnWKP.s
 GNU CPP version 3.0.3 (cpplib)
 GNU C++ version 3.0.3 (alphaev67-dec-osf5.1)
         compiled by GNU C version 3.0.3.
 ignoring nonexistent directory "/homes/iphuthep/kreckel/DUX4/alphaev67-dec-osf5.1/include"
 ignoring duplicate directory "base"
 #include "..." search starts here:
 #include <...> search starts here:
  /homes/iphuthep/kreckel/DUX4/include
  ../include
  integer
  base/digitseq
  base/digit
  base
  /homes/iphuthep/kreckel/DUX4/include/g++-v3
  /homes/iphuthep/kreckel/DUX4/include/g++-v3/alphaev67-dec-osf5.1
  /homes/iphuthep/kreckel/DUX4/include/g++-v3/backward
  /usr/local/include
  /homes/iphuthep/kreckel/DUX4/lib/gcc-lib/alphaev67-dec-osf5.1/3.0.3/include
  /usr/include
 End of search list.
  as -g -oldas -c -nocpp -O0 -o cl_0_ring.o /tmp/ccHKnWKP.s
  /homes/iphuthep/kreckel/DUX4/lib/gcc-lib/alphaev67-dec-osf5.1/3.0.3/mips-tfile -v -o cl_0_ring.o /tmp/ccHKnWKP.s
 mips-tfile version 3.0.3
 
 Regards
     -richy.
 -- 
 Richard B. Kreckel
 <Richard.Kreckel@Uni-Mainz.DE>
 <http://wwwthep.physik.uni-mainz.de/~kreckel/>
 
 


             reply	other threads:[~2002-02-20 17:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20  9:36 Richard B. Kreckel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-10  5:36 Rainer Orth
2002-05-10  5:27 ro
2002-05-09 10:56 Richard B. Kreckel
2002-04-16 10:56 Rainer Orth
2002-02-25  8:58 Rainer Orth
2002-02-23 14:12 Richard B. Kreckel
2002-02-22 15:46 Rainer Orth
2002-02-22 14:16 Rainer Orth
2002-02-21 16:21 Richard B. Kreckel
2002-02-19  5:26 Rainer Orth
2002-02-18 12:56 Richard B. Kreckel
2002-02-04 11:06 Rainer Orth
2002-02-04 11:06 Richard B. Kreckel
2002-01-30  6:14 ro
2002-01-27  6:26 kreckel

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=20020220172600.20558.qmail@sources.redhat.com \
    --to=kreckel@ginac.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=ro@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).