public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Ulrich Jakobus" <jakobus@emss.co.za>
To: toon@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/5914: Infinite loop when compiling with optimisation on of z_log.c of libf2c
Date: Mon, 11 Mar 2002 21:16:00 -0000	[thread overview]
Message-ID: <20020312051610.2378.qmail@sources.redhat.com> (raw)

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

From: "Ulrich Jakobus" <jakobus@emss.co.za>
To: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>,
	"gcc-gnats@gcc.gnu.org" <gcc-gnats@gcc.gnu.org>,
	"gcc-prs@gcc.gnu.org" <gcc-prs@gcc.gnu.org>,
	"jakobus@emss.co.za" <jakobus@emss.co.za>,
	"nobody@gcc.gnu.org" <nobody@gcc.gnu.org>,
	"toon@gcc.gnu.org" <toon@gcc.gnu.org>
Cc:  
Subject: Re: c/5914: Infinite loop when compiling with optimisation on of z_log.c of libf2c
Date: Tue, 12 Mar 2002 07:13:05 +0200

 >    
 >    Why are you submitting this ?
 >
 Sorry, may be a misunderstanding: I am using gcc-3.0.4 to compile
 the file z_log.c of libf2c myself, I am not referring to g77 and
 libf2c that comes with g77. I need my own version of libf2c for
 several reasons (modified variable mappings in the header file f2c.h
 and certain other defines in the makefiles deviating from the standard).
 
 OK, now I know that I should probably use "-O2 -ffloat-store" for
 the compilation, and not "-O3" or just "-O2" (which I have always
 done for previous releases of gcc).
 
 Thanks,
 
 Ulrich
 
 
 


             reply	other threads:[~2002-03-12  5:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-11 21:16 Ulrich Jakobus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-16  7:56 toon
2002-03-13 14:06 Toon Moene
2002-03-12 21:06 Ulrich Jakobus
2002-03-12 13:06 Toon Moene
2002-03-11 13:59 toon
2002-03-11 13:16 Tim Prince
2002-03-11  7:56 jakobus

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=20020312051610.2378.qmail@sources.redhat.com \
    --to=jakobus@emss.co.za \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=toon@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).