From: Filip Navara <navaraf@reactos.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] gcc4 host support
Date: Sat, 14 May 2005 09:55:11 +0200 [thread overview]
Message-ID: <4285AEDF.7040901@reactos.com> (raw)
In-Reply-To: <200505121800.40417.paul@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 321 bytes --]
Paul Brook wrote:
>On Wednesday 11 May 2005 22:04, Paul Brook wrote:
>
>
>>The attached patch adds support for gcc4 x86 and x86_64 hosts.
>>
>>
>
>This time with the correct patch attached.
>
>Paul
>
>
In addition to this patch I also needed the attached patch to get MinGW
GCC 3.4.1 builds working...
- Filip
[-- Attachment #2: qemu-gcc4-mingw.diff --]
[-- Type: text/x-patch, Size: 1376 bytes --]
--- dyngen.c Sat May 14 09:48:34 2005
+++ dyngen.c Sat May 14 09:37:13 2005
@@ -2255,7 +2255,8 @@ void gen_code(const char *name, host_ulo
for(i = 0, sym = symtab; i < nb_syms; i++, sym++) {
sym_name = get_sym_name(sym);
- if (strstart(sym_name, "__op_label", &p)) {
+ if (strstart(sym_name, "__op_label", &p) ||
+ strstart(sym_name, "_op_label", &p)) {
uint8_t *ptr;
unsigned long offset;
--- exec-all.h Sat May 14 09:48:34 2005
+++ exec-all.h Sat May 14 09:37:04 2005
@@ -349,12 +349,20 @@ do {\
#else
+#if __GNUC__ == 3 && __GNUC_MINOR__ < 4
+#define UNUSED __attribute__((unused))
+#elif defined(__GNUC__)
+#define UNUSED __attribute__((used))
+#else
+#define UNUSED
+#endif
+
/* jump to next block operations (more portable code, does not need
cache flushing, but slower because of indirect jump) */
#define GOTO_TB(opname, tbparam, n)\
do {\
- static void __attribute__((unused)) *dummy ## n = &&dummy_label ## n;\
- static void __attribute__((unused)) *__op_label ## n = &&label ## n;\
+ static void UNUSED *dummy ## n = &&dummy_label ## n;\
+ static void UNUSED *__op_label ## n = &&label ## n;\
goto *(void *)(((TranslationBlock *)tbparam)->tb_next[n]);\
label ## n: ;\
dummy_label ## n: ;\
next prev parent reply other threads:[~2005-05-14 8:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 21:04 [Qemu-devel] [patch] gcc4 host support Paul Brook
2005-05-12 17:00 ` Paul Brook
2005-05-12 22:13 ` Pascal Terjan
2005-05-12 22:25 ` Paul Brook
2005-05-14 7:55 ` Filip Navara [this message]
2005-05-14 11:53 ` Paul Brook
2005-05-14 11:56 ` Filip Navara
2005-06-17 4:30 ` [Qemu-devel] Fedora 4 + GCC4 + Qemu WAS: " Darryl Dixon
2005-06-17 12:45 ` Paul Brook
[not found] ` <1119013084.5187.4.camel@darrylsfc3box>
2005-06-17 13:02 ` Paul Brook
2005-06-17 22:18 ` David Woodhouse
2005-06-20 1:18 ` Darryl Dixon
2005-05-16 9:41 ` [Qemu-devel] " David Woodhouse
2005-05-17 20:46 ` Paul Brook
2005-05-18 10:06 ` Herbert Poetzl
2005-05-18 16:02 ` Paul Brook
2005-05-18 16:10 ` David Woodhouse
2005-05-18 19:29 ` John Hogerhuis
2005-05-18 20:48 ` Paul Brook
2005-05-18 20:55 ` David Woodhouse
2005-05-18 21:16 ` Paul Brook
2005-05-18 21:29 ` jeebs
2005-05-18 22:37 ` Paul Brook
2005-05-18 23:05 ` Ian Rogers
2005-05-18 22:37 ` Ian Rogers
2005-05-19 7:23 ` Gwenole Beauchesne
2005-05-19 13:20 ` Paul Brook
2005-05-19 14:07 ` Gwenole Beauchesne
2005-05-19 15:44 ` Paul Brook
2005-05-19 18:14 ` Thomas Steffen
2005-05-19 18:52 ` Paul Brook
2005-05-19 19:38 ` Tim Walker
2005-05-19 19:45 ` Paul Brook
2005-05-19 21:03 ` Thomas Steffen
2005-05-19 22:25 ` John Hogerhuis
2005-05-20 9:59 ` Thomas Steffen
2005-05-20 12:57 ` Paul Brook
2005-05-19 16:18 ` Ian Rogers
2005-05-19 13:47 ` McMullan, Jason
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=4285AEDF.7040901@reactos.com \
--to=navaraf@reactos.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.