From: "Tobias Schlüter" <tobias.schlueter@physik.uni-muenchen.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Janne Blomqvist <blomqvist.janne@gmail.com>,
Fortran List <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: PR fortran/51727: make module files reproducible, question on C++ in gcc
Date: Mon, 15 Oct 2012 17:58:00 -0000 [thread overview]
Message-ID: <507C4C37.6050302@physik.uni-muenchen.de> (raw)
In-Reply-To: <20121014214455.GV584@tucnak.redhat.com>
On 2012-10-14 23:44, Jakub Jelinek wrote:
> On Mon, Oct 15, 2012 at 12:35:27AM +0300, Janne Blomqvist wrote:
>> On Sat, Oct 13, 2012 at 4:26 PM, Tobias Schlüter
>>> I'm putting forward two patches. One uses a C++ map to very concisely build
>>> up and handle the ordered list of symbols. This has three problems:
>>> 1) gfortran maintainers may not want C++isms (even though in this case
>>> it's very localized, and in my opinion very transparent), and
>
> Even if you prefer a C++isms, why don't you go for "hash-table.h"?
> std::map at least with the default allocator will just crash the compiler
> if malloc returns NULL (remember that we build with -fno-exceptions),
> while when you use hash-table.h (or hashtab.h) you get proper OOM diagnostics.
I don't know these parts of C++ very well, but maybe an easy fix,
addressing this once and for all, would be doing the equivalent of
"set_new_handler (gcc_unreachable)" (or maybe a wrapper around fatal
("out of memory")?) at some point during gcc's initialization? This
should have the desired effect, shouldn't it?
Cheers,
- Tobi
next prev parent reply other threads:[~2012-10-15 17:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 13:41 Tobias Schlüter
2012-10-13 13:51 ` Tobias Schlüter
2012-10-13 18:21 ` Diego Novillo
2012-10-13 18:23 ` Tobias Schlüter
2012-10-13 18:23 ` Diego Novillo
2012-10-13 22:48 ` Joseph S. Myers
2012-10-14 22:37 ` Janne Blomqvist
2012-10-15 0:31 ` Jakub Jelinek
2012-10-15 12:54 ` Tobias Schlüter
2012-10-15 17:58 ` Tobias Schlüter [this message]
2012-10-15 21:06 ` [PATCH] Install error handler for out-of-memory when using STL containers " Tobias Schlüter
2012-10-28 15:50 ` Ping: [PATCH] Install error handler for out-of-memory when using STL containers Tobias Schlüter
2012-10-29 9:48 ` Paul Richard Thomas
2012-10-29 17:38 ` Mike Stump
2012-11-03 9:17 ` Ping**2: " Tobias Schlüter
2012-10-15 13:12 ` PR fortran/51727: make module files reproducible, question on C++ in gcc Tobias Schlüter
2012-11-08 19:02 ` Tobias Schlüter
2012-11-29 10:40 ` Tobias Schlüter
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=507C4C37.6050302@physik.uni-muenchen.de \
--to=tobias.schlueter@physik.uni-muenchen.de \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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).