public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: chandra@ssl.org
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/5536: CFLAGS not propagated to libgcc Makefile
Date: Tue, 29 Jan 2002 22:46:00 -0000	[thread overview]
Message-ID: <20020130064356.1732.qmail@sources.redhat.com> (raw)


>Number:         5536
>Category:       bootstrap
>Synopsis:       CFLAGS not propagated to libgcc Makefile
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 29 22:46:03 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     chandra@ssl.org
>Release:        3.0.3
>Organization:
>Environment:
N/A
>Description:
As a test, I compiled gcc after editing top-level makefile to change CFLAGS & friends to aggressive optimization. Ran make (not make bootstrap, mind you...don't want to read _that_ much text) and tee'd output to logfile for careful scrutiny.

Everything appeared to be compiled with the specified options _except_ libgcc, which did not receive CFLAGS and could probably really benefit from a -arch= optimization :)
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="A"; name="A"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="A"


             reply	other threads:[~2002-01-30  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-29 22:46 chandra [this message]
2002-11-28  4:29 bangerth
2003-03-11 22:42 neroden

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=20020130064356.1732.qmail@sources.redhat.com \
    --to=chandra@ssl.org \
    --cc=gcc-gnats@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).