public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos at systemhalted dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug faq/5012] New: Why must glibc be compiled with optimizations enabled? Date: Sat, 08 Sep 2007 16:01:00 -0000 [thread overview] Message-ID: <20070908160051.5012.carlos@systemhalted.org> (raw) The question "Why must glibc be compiled with optimizations enabled?" comes up often on the mailing list. The following patch adds an answer to the FAQ. -- Summary: Why must glibc be compiled with optimizations enabled? Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: faq AssignedTo: aj at suse dot de ReportedBy: carlos at systemhalted dot org CC: glibc-bugs at sources dot redhat dot com GCC build triplet: * GCC host triplet: * GCC target triplet: * 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 reply other threads:[~2007-09-08 16:01 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-09-08 16:01 carlos at systemhalted dot org [this message] 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 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=20070908160051.5012.carlos@systemhalted.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: linkBe 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).