public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lindevel at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/33992] Building libstdc++-v3: include/limits: stray '\275' in program
Date: Sun, 04 Nov 2007 02:02:00 -0000	[thread overview]
Message-ID: <20071104020231.1606.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33992-13189@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from lindevel at gmx dot net  2007-11-04 02:02 -------
Created an attachment (id=14481)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14481&action=view)
build.log


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33992


  parent reply	other threads:[~2007-11-04  2:02 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-04  1:37 [Bug bootstrap/33992] New: Building libstdc++-v3: include/limits: stray &#8216;\275&#8217; " lindevel at gmx dot net
2007-11-04  1:38 ` [Bug bootstrap/33992] Building libstdc++-v3: include/limits: stray '\275' " lindevel at gmx dot net
2007-11-04  2:02 ` lindevel at gmx dot net [this message]
2007-11-04  6:31 ` pinskia at gcc dot gnu dot org
2007-11-04 11:47 ` lindevel at gmx dot net
2007-11-09  9:50 ` lindevel at gmx dot net
2007-11-10  6:42 ` dirtyepic at gentoo dot org
2007-11-10 15:57 ` dirtyepic at gentoo dot org
2007-11-11  2:42 ` dirtyepic at gentoo dot org
2007-12-04 17:43 ` h dot mth at web dot de
2007-12-05 13:01 ` h dot mth at web dot de
2008-01-21 20:41 ` stefaan dot deroeck at gmail dot com
2008-02-04 20:31 ` dirtyepic at gentoo dot org
2008-02-06  1:20 ` bangerth at dealii dot org
2008-02-06  9:28 ` [Bug bootstrap/33992] [4.3 Regression] profiledbootstrap is broken rguenth at gcc dot gnu dot org
2008-02-06 10:00 ` rguenth at gcc dot gnu dot org
2008-02-06 11:20 ` rguenth at gcc dot gnu dot org
2008-02-06 20:51 ` rguenth at gcc dot gnu dot org
2008-02-07 20:48 ` ubizjak at gmail dot com
2008-02-08 14:22 ` ubizjak at gmail dot com
2008-02-08 20:16 ` ubizjak at gmail dot com
2008-02-08 20:25 ` ubizjak at gmail dot com
2008-02-08 21:18 ` ubizjak at gmail dot com
2008-02-08 21:29 ` rguenth at gcc dot gnu dot org
2008-02-09 21:05 ` [Bug middle-end/33992] [4.3 Regression] profiledbootstrap is broken (miscompiling a function with inlining) ubizjak at gmail dot com
2008-02-09 21:06 ` ubizjak at gmail dot com
2008-02-10  8:23 ` [Bug middle-end/33992] [4.3 Regression] Miscompiles a function, breaks profiledbootstrap ubizjak at gmail dot com
2008-02-10 10:45 ` [Bug middle-end/33992] [4.3 Regression] Miscompiles a function with inlining, " ubizjak at gmail dot com
2008-02-10 11:11 ` [Bug middle-end/33992] [4.3 Regression] Miscompiles " ubizjak at gmail dot com
2008-02-10 12:28 ` ubizjak at gmail dot com
2008-02-10 12:31 ` [Bug tree-optimization/33992] " ubizjak at gmail dot com
2008-02-10 13:46 ` ubizjak at gmail dot com
2008-02-10 13:49 ` pinskia at gcc dot gnu dot org
2008-02-10 14:32 ` ubizjak at gmail dot com
2008-02-10 14:33 ` ubizjak at gmail dot com
2008-02-10 22:09 ` rguenth at gcc dot gnu dot org
2008-02-10 22:37 ` rguenth at gcc dot gnu dot org
2008-02-10 22:44 ` rguenth at gcc dot gnu dot org
2008-02-11  1:35 ` dirtyepic at gentoo dot org
2008-02-11  8:28 ` rguenth at gcc dot gnu dot org
2008-02-11  9:00 ` ubizjak at gmail dot com
2008-02-15 13:40 ` ubizjak at gmail dot com

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=20071104020231.1606.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).