public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Eric <plukje@gmx.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/7537: GCC 3.1.1 ICE on GNU libiconv 1.8
Date: Wed, 08 Jan 2003 10:26:00 -0000	[thread overview]
Message-ID: <20030108102607.18959.qmail@sources.redhat.com> (raw)

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

From: Eric <plukje@gmx.net>
To: bangerth@dealii.org,  gcc-bugs@gcc.gnu.org,  gcc-prs@gcc.gnu.org, 
 nobody@gcc.gnu.org,  plukje@koekjes.net,  gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c/7537: GCC 3.1.1 ICE on GNU libiconv 1.8
Date: Wed, 08 Jan 2003 11:21:58 +0100

 bangerth@dealii.org wrote:
 
 >Synopsis: GCC 3.1.1 ICE on GNU libiconv 1.8
 >
 >State-Changed-From-To: open->feedback
 >State-Changed-By: bangerth
 >State-Changed-When: Tue Jan  7 18:09:43 2003
 >State-Changed-Why:
 >    I tried to reproduce your problem, but failed. But then,
 >    the report does not show the exact compile flags you
 >    used (I guess it might have been just -g, but am unsure)
 >    and on which of the two files the problem occured. Could
 >    you possibly send us the compile command that triggers
 >    the error?
 >    
 >    Thanks
 >      Wolfgang
 >    
 >    PS: The "lfs machine" is an x86-linux, right?
 >
 >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7537
 >
 Yup, it's a pentium 3 coppermine running at 667mhz (not overclocked).
 
 In order to create the problem I used as optimalization flags:
 "-O3 -march=i686 -mcpu=i686 -mmmx -msse"
 however, I was able to dupe the problem also using only:
 "-O"
 In order to do get the library to compile I had to specify
 to only use: "-g"  
 
 
 The libiconv library came from ftp.gnu.org, I'm unsure which version
 it was since it's been a while ago already.
 
 
 hope it helps,
 
 
 Eric
 
 
 
 


             reply	other threads:[~2003-01-08 10:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 10:26 Eric [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-08 16:53 bangerth
2003-01-08  2:09 bangerth
2002-08-08  3:16 plukje

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=20030108102607.18959.qmail@sources.redhat.com \
    --to=plukje@gmx.net \
    --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).