From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Yoshinori Sato <ysato@users.sourceforge.jp>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Tony Breeds <tony@bakeyournoodle.com>, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] h8300 fixes
Date: Sat, 2 Jun 2012 22:35:34 +0200 [thread overview]
Message-ID: <1338669339-23214-1-git-send-email-geert@linux-m68k.org> (raw)
Hi Sato-san, Andrew,
The following patch set makes h8300 defconfig build again.
Due to lack of hardware, there's no guarantee this makes it actually boot.
I used the h8300-elf-gcc from
http://kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.3/.
I had two issues with this compiler, though:
1. I got 2 ICEs:
fs/read_write.c: In function 'sys_pread64':
fs/read_write.c:514:1: internal compiler error: in based_loc_descr, at dwarf2out.c:13636
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[4]: *** [fs/read_write.o] Error 1
CC fs/dcache.o
fs/dcache.c: In function '__d_path':
fs/dcache.c:2662:1: internal compiler error: in based_loc_descr, at dwarf2out.c:13636
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
2. I also got several warnings of the form:
warning: format '%zx' expects argument of type 'size_t', but argument 4 has type 'unsigned int'
while the actual parameter type is size_t, not unsigned int.
Could this be because the compiler is h8300-elf-gcc and not h8300-linux-gcc?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2012-06-02 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 20:35 Geert Uytterhoeven [this message]
2012-06-02 20:35 ` [PATCH 1/5] h8300/pgtable: Add missing #include <asm-generic/pgtable.h> Geert Uytterhoeven
2012-06-02 20:35 ` [PATCH 2/5] h8300/signal: Fix typo "statis" Geert Uytterhoeven
2012-06-02 21:37 ` Al Viro
2012-06-04 0:13 ` Tony Breeds
2012-06-02 20:35 ` [PATCH 3/5] h8300/time: Add missing #include <asm/irq_regs.h> Geert Uytterhoeven
2012-06-02 20:35 ` [PATCH 4/5] h8300/uaccess: Remove assignment to __gu_val in unhandled case of get_user() Geert Uytterhoeven
2012-06-02 20:35 ` [PATCH 5/5] h8300/uaccess: Add mising __clear_user() Geert Uytterhoeven
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=1338669339-23214-1-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@bakeyournoodle.com \
--cc=ysato@users.sourceforge.jp \
/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).