public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Jari Häkkinen" <jari@chiralcomp.com>
To: Achim Gaedke <Achim.Gaedke@uni-koeln.de>
Cc: gsl-discuss@sources.redhat.com
Subject: Re: Problems compiling tests with gcc 3.1
Date: Fri, 31 May 2002 12:45:00 -0000	[thread overview]
Message-ID: <3CF7C8BB.9070107@chiralcomp.com> (raw)
Message-ID: <20020531124500.ivgGlLNSutuoRqd99762sr0DG-mhNcr_yLShgoMXzIA@z> (raw)
In-Reply-To: <3CF7AFDC.14CCE203@uni-koeln.de>

Thanks for testing. I'll submit a bug report to the gcc development team 
during the weekend.

Jari


Achim Gaedke wrote:

> Hi Jari!
> 
> I stated, that I was successful with gcc-3.1 and redhat7.3, but that was due to
> 
> CFLAGS="-O0 -g"
> 
> no optimization. With the default CFLAGS="-O2 -g" I had the same error.
> 
> /opt/gcc-3.1/bin/gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I..    -g -O2 -c test.c
> In file included from test.c:61:
> test_complex_source.c: In function `test_complex_float_trap':
> test_complex_source.c:258: Internal compiler error in subst, at combine.c:3546
> 
> This is an abort statement in gcc-3.1/gcc/combine.c .
> 
> I DO agree with Brian, that this error MUST be reported to gcc. If you need help
> with the bug report, please ask.
> 
> Yours, Achim
> 
> Jari Häkkinen schrieb:
> 
>>Hi.
>>
>>I have problems running (compiling) some of the test programs with gcc
>>version 3.1. The test programs compile using gcc 2.95.
>>
>>I am working with gsl 1.1.1, and compiling ('make' with gcc 3.1) the
>>projects works alright. When running 'make check' all directories,
>>except vector and matrix, compiles and passes all tests. In the matrix
>>and vector directories, gcc gives the following output:
>>
>>gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I..    -g -O2 -c test_static.c
>>In file included from test.c:61,
>>                  from test_static.c:6:
>>test_complex_source.c: In function `test_complex_float_trap':
>>test_complex_source.c:258: Internal compiler error in subst, at
>>combine.c:3546
>>Please submit a full bug report,
>>with preprocessed source if appropriate.
>>See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>>make[2]: *** [test_static.o] Error 1
>>
>>I have not submitted a bug-report. Is this a known problem?
>>
>>Jari
>>
>>--
>>Jari Häkkinen, PhD
>>Complex Systems Division                        mailto:jari@thep.lu.se
>>Department of Theoretical Physics               phone: +46 (0)46 2220667
>>Lund University                                 fax:   +46 (0)46 2229686
>>Sölvegatan 14a, SE-223 62 Lund, Sweden          http://www.thep.lu.se
>>


-- 
Jari Häkkinen                                  tel: +46 (0)40 320697
mailto:jari@chiralcomp.com                     http://www.chiralcomp.com

  parent reply	other threads:[~2002-05-31 19:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-31  9:55 Jari Häkkinen
2002-05-29  3:46 ` Jari Häkkinen
2002-12-31  9:55 ` Achim Gaedke
2002-05-31 10:45   ` Achim Gaedke
2002-12-31  9:55   ` Jari Häkkinen [this message]
2002-05-31 12:45     ` Jari Häkkinen
2002-12-31  9:55 ` Brian Gough
2002-05-30  4:59   ` Brian Gough
2002-12-31  9:55   ` John Ketchum
2002-05-31 10:17     ` John Ketchum
     [not found] <Pine.GSO.3.95.1020529133453.5635A-100000@Octopussy>
2002-12-31  9:55 ` Jari Häkkinen
2002-05-29 11:27   ` Jari Häkkinen

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=3CF7C8BB.9070107@chiralcomp.com \
    --to=jari@chiralcomp.com \
    --cc=Achim.Gaedke@uni-koeln.de \
    --cc=gsl-discuss@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).