public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/39326] Segmentation fault with -O1, out of memory with -O2
Date: Thu, 07 Mar 2013 10:15:00 -0000 [thread overview]
Message-ID: <bug-39326-4-5llGU1QXBl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-39326-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39326
--- Comment #33 from rguenther at suse dot de <rguenther at suse dot de> 2013-03-07 10:14:53 UTC ---
On Thu, 7 Mar 2013, steven at gcc dot gnu.org wrote:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39326
>
> Steven Bosscher <steven at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|NEW |ASSIGNED
> AssignedTo|unassigned at gcc dot |steven at gcc dot gnu.org
> |gnu.org |
>
> --- Comment #31 from Steven Bosscher <steven at gcc dot gnu.org> 2013-03-07 09:58:03 UTC ---
> (In reply to comment #30)
> Hmm, RTL PRE isn't really mine either, but I probably know it as well as
> anyone else, so I will have a look. It's probably a similar issue as for
> gimple LIM: alias checks.
>
> Can you attach your TLC patches for gimple LIM to this PR, please?
Bah, I seem to have them in some local tree only but cannot find it.
Maybe I accidentially reverted :/
ISTR moving stuff to obstacks as well (LIM has the heaviest load on
malloc/free).
Oh well.
next prev parent reply other threads:[~2013-03-07 10:15 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-39326-4@http.gcc.gnu.org/bugzilla/>
2013-03-06 11:08 ` steven at gcc dot gnu.org
2013-03-06 11:38 ` rguenth at gcc dot gnu.org
2013-03-06 16:50 ` sergstesh at yahoo dot com
2013-03-06 23:39 ` steven at gcc dot gnu.org
2013-03-07 0:08 ` steven at gcc dot gnu.org
2013-03-07 0:27 ` steven at gcc dot gnu.org
2013-03-07 8:10 ` steven at gcc dot gnu.org
2013-03-07 8:45 ` rguenther at suse dot de
2013-03-07 8:48 ` rguenther at suse dot de
2013-03-07 8:53 ` rguenther at suse dot de
2013-03-07 9:58 ` steven at gcc dot gnu.org
2013-03-07 10:14 ` sergstesh at yahoo dot com
2013-03-07 10:15 ` rguenther at suse dot de [this message]
2013-03-07 17:14 ` sergstesh at yahoo dot com
2013-03-07 17:31 ` steven at gcc dot gnu.org
2013-03-07 17:34 ` steven at gcc dot gnu.org
2013-03-07 21:48 ` sergstesh at yahoo dot com
2013-03-07 22:16 ` steven at gcc dot gnu.org
2013-03-07 23:19 ` steven at gcc dot gnu.org
2013-03-08 9:14 ` rguenth at gcc dot gnu.org
2013-03-08 9:14 ` rguenth at gcc dot gnu.org
2013-03-08 9:23 ` rguenther at suse dot de
2013-03-09 14:58 ` steven at gcc dot gnu.org
2013-03-09 17:26 ` steven at gcc dot gnu.org
2013-03-11 9:40 ` steven at gcc dot gnu.org
2013-03-12 10:47 ` rguenth at gcc dot gnu.org
2013-03-12 14:05 ` rguenth at gcc dot gnu.org
2013-03-15 16:07 ` rguenth at gcc dot gnu.org
2013-03-18 8:44 ` rguenth at gcc dot gnu.org
2013-03-21 20:04 ` jakub at gcc dot gnu.org
2013-03-22 14:01 ` rguenth at gcc dot gnu.org
2013-03-26 10:10 ` rguenth at gcc dot gnu.org
2014-01-15 15:14 ` rguenth at gcc dot gnu.org
2014-01-17 13:53 ` rguenth at gcc dot gnu.org
2022-03-10 15:05 ` rguenth at gcc dot gnu.org
2024-02-20 13:14 ` rguenth at gcc dot gnu.org
2009-02-28 15:23 [Bug c/39326] New: " sergstesh at yahoo dot com
2009-03-02 17:16 ` [Bug middle-end/39326] " pinskia at gcc dot gnu dot org
2009-03-03 13:36 ` sergstesh at yahoo dot com
2009-03-03 13:49 ` rguenther at suse dot de
2009-03-03 14:15 ` sergstesh at yahoo dot com
2009-03-17 11:05 ` rguenth at gcc dot gnu dot org
2009-03-17 12:42 ` rguenth at gcc dot gnu dot org
2009-03-17 12:59 ` rguenth at gcc dot gnu dot org
2009-03-17 13:10 ` rguenth at gcc dot gnu dot 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-39326-4-5llGU1QXBl@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).