From: Thorsten Kukuk <kukuk@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Illegal instruction on sparc32-linux
Date: Fri, 19 Apr 2002 02:51:00 -0000 [thread overview]
Message-ID: <20020419114721.A8609@suse.de> (raw)
In-Reply-To: <20020418.144050.39820645.davem@redhat.com>
On Thu, Apr 18, David S. Miller wrote:
>
> From: Thorsten Kukuk <kukuk@suse.de>
> Date: Thu, 18 Apr 2002 22:11:51 +0200
>
> If I compile C++ programs with the latest gcc 3.1 snapshots on
> sparc32-linux, some programs fails with "Illegal instruction".
>
> This is reproduceable for me with groff, qt2 and qt3. Does anybody
> else see this?
>
> Can you put the program under GDB so we can see what the instruction
> is that it is trapping on?
I tried it. But when I compile it with -g, I cannot reproduce it from
the shell or from gdb. But if I call "make", it fails again.
> I'm not seeing this at all, but I only do testing on UltraSPARC boxes
> for the sparc32 targets...
I also use a UltraSPARC for this. I compile groff and then run
"sparc32 make" in the groff/doc source directory and it fails
with:
export GROFF_TMAC_PATH; \
sed -e "s;@VERSION@;`cat ../VERSION``sed -e 's/^0$//' -e 's/^[1-9].*$/.&/' ../RE
VISION`;" pic.ms \
| ../src/roff/groff/groff -p -e -t -Tps -F../font -U -ms -mwww >pic.ps
../src/roff/groff/groff: troff: Illegal instruction
All other input files works fine. Same for uic from qt2 and qt3: If
I try to debug it, it works. And there are only a few input files
for which it fails, most input files works fine.
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE Linux AG Deutschherrenstr. 15-19 D-90429 Nuernberg
--------------------------------------------------------------------
Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
next prev parent reply other threads:[~2002-04-19 9:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 13:18 Thorsten Kukuk
2002-04-18 13:32 ` Christian Jönsson
2002-04-18 14:51 ` David S. Miller
2002-04-19 2:51 ` Thorsten Kukuk [this message]
2002-04-19 3:40 ` David S. Miller
2002-04-19 4:45 ` Thorsten Kukuk
2002-04-19 9:03 ` David S. Miller
2002-04-19 9:20 ` Thorsten Kukuk
2002-04-24 7:07 ` David S. Miller
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=20020419114721.A8609@suse.de \
--to=kukuk@suse.de \
--cc=davem@redhat.com \
--cc=gcc@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).