public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jbglaw at lug-owl dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/15491] ICE (Internal compiler error) while compiling glibc to vax-linux target
Date: Wed, 30 Jun 2004 06:48:00 -0000 [thread overview]
Message-ID: <20040630062543.14579.qmail@sourceware.org> (raw)
In-Reply-To: <20040517103549.15491.gabucino@mplayerhq.hu>
------- Additional Comments From jbglaw at lug-owl dot de 2004-06-30 06:25 -------
Subject: Re: ICE (Internal compiler error) while compiling glibc to vax-linux target
On Wed, 2004-06-30 02:55:52 -0000, danglin at gcc dot gnu dot org <gcc-bugzilla@gcc.gnu.org>
wrote in message <20040630025552.9449.qmail@sourceware.org>:
>
> ------- Additional Comments From danglin at gcc dot gnu dot org 2004-06-30 02:55 -------
> > At least, it looks even a bit better and does make some sense:) For now,
> > I don't think that cycle costs are the largest problem for VAX (the VAX
> > backend was even mentioned to be removed completely...).
>
> I wasn't too concerned about the cost calculation. If the code fragment
> doesn't fix the original problem, can you try in gdb
>
> p debug_rtx (x)
>
> so that we can see in more detail the rtx that caused the problem? It
> might be necessary to break on vax_rtx_costs_1 with x==0x40273ea0 and
> step though the routine.
A good first introduction into GCC debugging:) Thanks. Any chance to
organize some hacker's meeting in Europe to let you teach first steps in
GCC hacking? Maybe you'd come over to the Oldenburger Linuxtag's Kernel
Hacker's meeting (mostly Linux), that would take care for proper
audience.
MfG, JBG
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15491
next prev parent reply other threads:[~2004-06-30 6:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 20:15 [Bug c/15491] New: " gabucino at mplayerhq dot hu
2004-05-17 20:21 ` [Bug c/15491] " gabucino at mplayerhq dot hu
2004-05-17 20:43 ` gabucino at mplayerhq dot hu
2004-05-17 22:07 ` [Bug target/15491] " jbglaw at lug-owl dot de
2004-05-17 22:07 ` pinskia at gcc dot gnu dot org
2004-05-27 21:07 ` jbglaw at lug-owl dot de
2004-05-27 21:35 ` jbglaw at lug-owl dot de
2004-05-27 23:56 ` pinskia at gcc dot gnu dot org
2004-05-28 0:05 ` jbglaw at lug-owl dot de
2004-05-28 1:21 ` jbglaw at lug-owl dot de
2004-05-28 23:27 ` jbglaw at lug-owl dot de
2004-06-25 3:27 ` danglin at gcc dot gnu dot org
2004-06-26 15:24 ` jbglaw at lug-owl dot de
2004-06-29 3:03 ` pinskia at gcc dot gnu dot org
2004-06-30 2:50 ` danglin at gcc dot gnu dot org
2004-06-30 2:55 ` danglin at gcc dot gnu dot org
2004-06-30 6:22 ` jbglaw at lug-owl dot de
2004-06-30 6:25 ` jbglaw at lug-owl dot de
2004-06-30 6:48 ` jbglaw at lug-owl dot de [this message]
2004-06-30 7:57 ` jbglaw at lug-owl dot de
2005-01-09 15:45 ` danglin at gcc dot gnu dot org
2005-01-09 15:59 ` pinskia at gcc dot gnu dot org
2005-01-09 16:09 ` danglin at gcc dot gnu dot org
2005-03-25 17:31 ` cvs-commit at gcc dot gnu dot org
2005-03-25 17:55 ` cvs-commit at gcc dot gnu dot org
2005-03-25 18:31 ` cvs-commit at gcc dot gnu dot org
2005-03-25 19:28 ` danglin at gcc dot gnu dot org
2005-03-25 19:39 ` 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=20040630062543.14579.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).