From: Anton Blanchard <anton@samba.org>
To: paulus@samba.org, benh@kernel.crashing.org, akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gcc 3.5 fixes
Date: Sun, 4 Jul 2004 17:07:02 +1000 [thread overview]
Message-ID: <20040704070702.GC4923@krispykreme> (raw)
In-Reply-To: <20040704070144.GB4923@krispykreme>
gcc 3.5 ICEd on the ppc64 version of __ptep_set_access_flags, but it does
look like we want to use *ptep here.
Signed-off-by: Anton Blanchard <anton@samba.org>
diff -ur /root/toolchain/linux-2.5-bk/include/asm-ppc64/pgtable.h linux-2.5-bk/include/asm-ppc64/pgtable.h
--- /root/toolchain/linux-2.5-bk/include/asm-ppc64/pgtable.h 2004-06-13 14:37:00.000000000 +0000
+++ linux-2.5-bk/include/asm-ppc64/pgtable.h 2004-07-03 12:01:10.522949800 +0000
@@ -424,7 +424,7 @@
stdcx. %0,0,%4\n\
bne- 1b"
:"=&r" (old), "=&r" (tmp), "=m" (*ptep)
- :"r" (bits), "r" (ptep), "m" (ptep), "i" (_PAGE_BUSY)
+ :"r" (bits), "r" (ptep), "m" (*ptep), "i" (_PAGE_BUSY)
:"cc");
}
#define ptep_set_access_flags(__vma, __address, __ptep, __entry, __dirty) \
next prev parent reply other threads:[~2004-07-04 7:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 6:58 [PATCH] gcc 3.5 fixes Anton Blanchard
2004-07-04 7:01 ` Anton Blanchard
2004-07-04 7:07 ` Anton Blanchard [this message]
2004-07-04 10:24 ` Bartlomiej Zolnierkiewicz
2004-07-04 11:04 ` Anton Blanchard
2004-07-06 15:28 ` Randy.Dunlap
2004-07-11 10:23 ` Anton Blanchard
[not found] <2e9is-5YT-1@gated-at.bofh.it>
[not found] ` <2e9iu-5YT-5@gated-at.bofh.it>
[not found] ` <2ecq2-80i-1@gated-at.bofh.it>
[not found] ` <7ab39013.0407042237.40ea9035@posting.google.com>
[not found] ` <20040705064010.C9BFB5F7AA@attila.bofh.it>
2004-07-05 16:51 ` Mark Adler
2004-07-05 21:44 ` Paul Jackson
2004-07-06 1:16 ` Mark Adler
2004-07-06 1:45 ` Paul Jackson
2004-07-06 3:51 ` Jesse Stockall
2004-07-06 4:43 ` Mark Adler
2004-07-06 6:11 ` bert hubert
2004-07-06 6:46 ` David Woodhouse
2004-07-06 15:02 ` Mark Adler
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=20040704070702.GC4923@krispykreme \
--to=anton@samba.org \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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.