From: "developer@isl-gbr.de" <developer@isl-gbr.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] X86_64 (AMD64) build segfaults
Date: Sat, 23 Apr 2005 11:06:27 +0200 [thread overview]
Message-ID: <20050423110627.5023b57b@smirftschs.home.tld> (raw)
In-Reply-To: <200504221249.46257.jkim@niksun.com>
didnt find any searching through the buglist, dont know why, but i sent it already, sry :)
Any ideas when 3.4.4 will be released ?
On Fri, 22 Apr 2005 12:49:46 -0400
Jung-uk Kim <jkim@niksun.com> wrote:
> > when trying to compile qemu i get always a segfault. My system is
> > uniarch x86_64, cc version 3.4.3, did happen with 3.3 too.
> >
> > tried snapshot and 0.6.1, no difference - getting only
> >
> > target-i386/op.c:374: internal compiler error: Segmentation fault
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
>
> https://bugzilla.redhat.com/beta/show_bug.cgi?id=138627
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17825
>
> Fixed in GCC 4.0.0 and GCC 3.4.4-20050317.
>
> > where to send the full bugreport to ?
>
> There are many duplicates already. So, don't do that. ;-)
>
> My 2 cents...
>
> Jung-uk Kim
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2005-04-23 9:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 16:49 [Qemu-devel] X86_64 (AMD64) build segfaults Jung-uk Kim
2005-04-23 9:06 ` developer [this message]
2005-05-02 17:40 ` Jung-uk Kim
-- strict thread matches above, loose matches on Subject: below --
2005-04-22 16:35 Jung-uk Kim
2005-04-21 14:34 developer
2005-04-21 14:42 ` Paul Brook
2005-04-21 14:59 ` developer
2005-04-21 15:01 ` Paul Brook
2005-04-21 16:02 ` developer
2005-04-22 14:50 ` developer
2005-04-22 15:01 ` Jonas Maebe
2005-04-22 15:41 ` developer
2005-04-22 16:12 ` Jonas Maebe
2005-04-22 16:30 ` developer
2005-04-22 16:33 ` Paul Brook
2005-04-23 9:05 ` developer
2005-04-23 11:33 ` Paul Brook
2005-04-22 22:12 ` Joshua Root
2005-04-21 15:11 ` Paul Brook
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=20050423110627.5023b57b@smirftschs.home.tld \
--to=developer@isl-gbr.de \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).