public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nospamname at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/40414] gcc 4.4.0 error at postreload.c:396
Date: Wed, 30 Dec 2009 12:07:00 -0000 [thread overview]
Message-ID: <20091230120657.24246.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40414-16717@http.gcc.gnu.org/bugzilla/>
------- Comment #24 from nospamname at web dot de 2009-12-30 12:06 -------
(In reply to comment #23)
> You need a proper patch, not instructions.
>
> However, it's clear from the bugreport and the patches required to fix it, that
> it is not important whether the target is m68k-amigaos or another OS.
>
Yes i know, and i can do a diff, but are there chances that this changes are
add or is m68k-amigaos going to remove complete in 4.6 ?
Wy can not the code stay in as long it work well ?
m68k-amigaos is a m68k bsd a.out Build that use sjlj Exception Handling on C++.
So there is no special support Code for AOS need and it work well with newest
compilers.
The only that need add to compile GCC and g++ is this.
add in gcc-x.x.x/gcc/config.gcc
(search for m68k)
m68k-*-amigaos*)
tmake_file=m68k/t-amigaos
tm_file="${tm_file} m68k/amigaos.h"
tm_p_file="${tm_p_file} m68k/amigaos-protos.h"
tm_defines="TARGET_AMIGAOS TARGET_DEFAULT=0" # 68040
extra_objs=amigaos.o
gnu_ld=yes
;;
more add in config files is only need for libgcc and libstdc++
When report a Bug, we can also compare the asm Code with a better support 68k
Target, thats no Problem, but we thought because of same C Code all work same.
But i like know what 68k target Andreas or other GCC Developer for 68k use and
what configure Options they use so i can build a cygwin Version for this
compilers.
Or is there a binary build for cygwin and these 68k Compilers here ?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40414
next prev parent reply other threads:[~2009-12-30 12:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 13:34 [Bug c/40414] New: " nospamname at web dot de
2009-06-11 13:52 ` [Bug c/40414] " schwab at linux-m68k dot org
2009-06-11 15:03 ` bonzini at gnu dot org
2009-06-15 19:36 ` [Bug target/40414] " gni at gecko dot de
2009-06-16 11:06 ` nospamname at web dot de
2009-08-02 7:23 ` nospamname at web dot de
2009-08-06 15:56 ` nospamname at web dot de
2009-08-17 19:25 ` ami_stuff at o2 dot pl
2009-08-17 19:33 ` ami_stuff at o2 dot pl
2009-08-17 20:11 ` ami_stuff at o2 dot pl
2009-08-17 20:11 ` ami_stuff at o2 dot pl
2009-08-19 0:28 ` ami_stuff at o2 dot pl
2009-08-19 10:38 ` mikpe at it dot uu dot se
2009-08-23 18:25 ` schwab at linux-m68k dot org
2009-08-27 10:39 ` nospamname at web dot de
2009-09-03 18:58 ` mikpe at it dot uu dot se
2009-12-29 16:31 ` schwab at linux-m68k dot org
2009-12-29 17:29 ` ami_stuff at o2 dot pl
2009-12-29 18:01 ` bonzini at gnu dot org
2009-12-29 18:45 ` nospamname at web dot de
2009-12-29 19:31 ` bonzini at gnu dot org
2009-12-29 21:44 ` joseph at codesourcery dot com
2009-12-30 9:40 ` nospamname at web dot de
2009-12-30 10:56 ` bonzini at gnu dot org
2009-12-30 12:07 ` nospamname at web dot de [this message]
2009-12-30 12:22 ` bonzini at gnu dot org
2010-04-06 11:28 ` rguenth at gcc dot gnu dot org
2010-07-31 9:35 ` rguenth at gcc dot gnu dot org
[not found] <bug-40414-4@http.gcc.gnu.org/bugzilla/>
2010-09-27 17:18 ` schwab@linux-m68k.org
2010-11-01 16:41 ` bonzini at 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=20091230120657.24246.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).