public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jh at suse dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/16460] [3.5 Regression] ICE when compiling glibc (ld-ctype.c)
Date: Fri, 10 Sep 2004 23:59:00 -0000 [thread overview]
Message-ID: <20040910235908.17055.qmail@sourceware.org> (raw)
In-Reply-To: <20040709202544.16460.drepper@redhat.com>
------- Additional Comments From jh at suse dot cz 2004-09-10 23:59 -------
Subject: Re: [3.5 Regression] ICE when compiling glibc (ld-ctype.c)
>
> ------- Additional Comments From rth at redhat dot com 2004-09-10 19:07 -------
> Subject: Re: [3.5 Regression] ICE when compiling glibc (ld-ctype.c)
>
> On Fri, Sep 10, 2004 at 12:34:10PM +0200, Jan Hubicka wrote:
> > Richard, does this seem sane? I probably should do that in
> > unnest_function_tree so it is done at the time unnesting really happens
> > instead of waiting for the end of compilation. I will do this change
> > before putting in the patch if this approach looks sane to you.
>
> I think I would prefer that. Provide a function in cgraph*.c to
> perform the cgraph_node manipulation, and call that from the end
> of tree-nested.c.
Yeah, sure, I didn't intend to commit the patch in the current form, I
just got short of time and I was unsure if you don't have different
approach in mind.
I will create updated version, thanks.
Honza
>
>
> r~
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16460
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16460
next prev parent reply other threads:[~2004-09-10 23:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 20:25 [Bug middle-end/16460] New: " drepper at redhat dot com
2004-07-09 20:27 ` [Bug middle-end/16460] " drepper at redhat dot com
2004-07-09 23:49 ` [Bug middle-end/16460] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-07-10 1:48 ` pinskia at gcc dot gnu dot org
2004-07-14 8:46 ` pinskia at gcc dot gnu dot org
2004-08-12 0:20 ` pinskia at gcc dot gnu dot org
2004-08-21 1:51 ` pinskia at gcc dot gnu dot org
2004-09-09 6:52 ` aj at gcc dot gnu dot org
2004-09-10 8:15 ` pinskia at gcc dot gnu dot org
2004-09-10 8:19 ` jh at suse dot cz
2004-09-10 10:34 ` jh at suse dot cz
2004-09-10 19:07 ` rth at redhat dot com
2004-09-10 23:59 ` jh at suse dot cz [this message]
2004-09-20 20:38 ` [Bug middle-end/16460] [4.0 " cvs-commit at gcc dot gnu dot org
2004-09-20 20:48 ` pinskia 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=20040910235908.17055.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).