public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/59431] [4.9 regression] runtime FAILs on Solaris
Date: Fri, 10 Jan 2014 17:04:00 -0000	[thread overview]
Message-ID: <bug-59431-4-zFFqi03i25@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59431-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Ian Lance Taylor <ian at airs dot com> ---
Yeah, I didn't think that would fix this problem, I was just hoping for more
consistent error messages--e.g., "out of memory" rather than "caught signal
while mallocing: 10".


  parent reply	other threads:[~2014-01-10 17:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 15:33 [Bug go/59431] New: " ro at gcc dot gnu.org
2013-12-09 15:34 ` [Bug go/59431] " ro at gcc dot gnu.org
2013-12-17 18:31 ` jakub at gcc dot gnu.org
2014-01-10  7:38 ` ubizjak at gmail dot com
2014-01-10  9:42 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-01-10 17:04 ` ian at airs dot com [this message]
2014-02-20 13:36 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-04-22 11:38 ` [Bug go/59431] [4.9/4.10 " jakub at gcc dot gnu.org
2014-07-16 13:31 ` jakub at gcc dot gnu.org
2014-10-30 11:29 ` [Bug go/59431] [4.9/5 " jakub at gcc dot gnu.org
2015-06-26 20:18 ` [Bug go/59431] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:39 ` jakub at gcc dot gnu.org
2021-05-14  9:47 ` [Bug go/59431] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:06 ` rguenth at gcc dot gnu.org
2022-05-27  9:35 ` [Bug go/59431] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:30 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug go/59431] [11/12/13/14 " rguenth at gcc dot gnu.org

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=bug-59431-4-zFFqi03i25@http.gcc.gnu.org/bugzilla/ \
    --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).