public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Thomas, Robert S" <robert.s.thomas@lmco.com>
To: "'gcc@gcc.gnu.org'" <gcc@gcc.gnu.org>
Subject: Optimization
Date: Thu, 11 May 2000 11:21:00 -0000	[thread overview]
Message-ID: <4B55904D9AC9D1119BA40000F81E49C703336DFD@emss04m10.ems.lmco.com> (raw)

Hello,	
	Can you help shed some light as to what exactly -fcombine_statics
optimization flag does?

We are using 2.7.2 and when we compile optimized (-O3) we get an internal
compiler error.  If this flag is removed everything compiled fine.  

We need to justify removing this flag from the compile line however we are
unclear as to what we are actually losing by doing so.

Any insight would be great

Thanks
Rob

robert.s.thomas@lmco.com

             reply	other threads:[~2000-05-11 11:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-11 11:21 Thomas, Robert S [this message]
2000-05-11 11:31 ` Optimization Jeffrey A Law
  -- strict thread matches above, loose matches on Subject: below --
2003-12-09 18:18 optimization Benjamin Kosnik
2003-12-09 16:42 optimization Viktor Przebinda
2003-12-09 17:29 ` optimization Diego Novillo
2003-12-09 18:53 ` optimization Scott Robert Ladd
2003-05-02 12:05 Optimization Piotr Wyderski
2003-05-02 23:08 ` Optimization Richard Henderson
2003-05-03  0:12   ` Optimization Andrew Pinski
2003-05-03  1:14     ` Optimization Richard Henderson
1999-03-30  5:07 Optimization Oskar Enoksson
1999-03-31 23:46 ` Optimization Oskar Enoksson
1998-03-29  5:14 Optimization Oskar Enoksson
1998-04-02  3:41 ` Optimization John Carr
1998-04-02  8:21 ` Optimization Jeffrey A Law
1998-04-02 11:32 ` Optimization Joern Rennecke
1998-04-02 11:32 ` Optimization Jim Wilson
1998-04-02  3:41   ` Optimization Oskar Enoksson
1998-04-03 21:52     ` Optimization John Carr
1999-03-29  8:18 ` Optimization Jeffrey A Law
1999-03-31 23:46   ` Optimization Jeffrey A Law

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=4B55904D9AC9D1119BA40000F81E49C703336DFD@emss04m10.ems.lmco.com \
    --to=robert.s.thomas@lmco.com \
    --cc=gcc@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).