public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug faq/5012] Why must glibc be compiled with optimizations enabled?
Date: Fri, 22 Feb 2008 09:58:00 -0000 [thread overview]
Message-ID: <20080222095758.18348.qmail@sourceware.org> (raw)
In-Reply-To: <20070908160051.5012.carlos@systemhalted.org>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2008-02-22 09:57 -------
Subject: Bug 5012
CVSROOT: /cvs/glibc
Module name: libc
Changes by: aj@sourceware.org 2008-02-22 09:57:19
Modified files:
. : FAQ.in
Log message:
[BZ #5012]
* FAQ.in: Describe why glibc needs to be compiled with
optimization.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/libc/FAQ.in.diff?cvsroot=glibc&r1=1.138&r2=1.139
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5012
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2008-02-22 9:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 16:01 [Bug faq/5012] New: " carlos at systemhalted dot org
2007-09-08 16:02 ` [Bug faq/5012] " carlos at systemhalted dot org
2007-09-08 16:04 ` carlos at systemhalted dot org
2007-10-06 17:02 ` drepper at redhat dot com
2007-10-28 5:25 ` aj at suse dot de
2008-02-08 14:01 ` carlos at systemhalted dot org
2008-02-08 14:02 ` carlos at systemhalted dot org
2008-02-21 17:34 ` carlos at codesourcery dot com
2008-02-21 17:35 ` carlos at codesourcery dot com
2008-02-22 9:58 ` cvs-commit at gcc dot gnu dot org [this message]
2008-02-22 10:02 ` aj at suse dot de
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=20080222095758.18348.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).