public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "h dot m dot brand at xs4all dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/26508] 4.1.0 doesn't build in 64bit on PA-RISC Date: Sun, 05 Mar 2006 16:46:00 -0000 [thread overview] Message-ID: <20060305164604.13333.qmail@sourceware.org> (raw) In-Reply-To: <bug-26508-11434@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from h dot m dot brand at xs4all dot nl 2006-03-05 16:46 ------- To Steven: I'm not pushing, but IMHO, I think it could be said that it is a bug in gcc if gcc does not generate valid HP PA-RISC assembly code *as understood by the native compiler*. To Andrew: For the last remark, what other version of binutils should/could I try? 2.16.1 was the most recent as far as I can see, and ftp://alpha.gnu.org/gnu/ doesn't have a binutils. I'm very willing to help here, and can try out almost anything. Would it help if I tried a more recent 4.2 snapshot? ftp://ftp.fu-berlin.de/unix/languages/gcc/snapshots/4.2-20060304/ -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26508
next prev parent reply other threads:[~2006-03-05 16:46 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-03-01 12:32 [Bug c/26508] New: " h dot m dot brand at xs4all dot nl 2006-03-01 12:56 ` [Bug target/26508] " h dot m dot brand at xs4all dot nl 2006-03-01 13:04 ` pinskia at gcc dot gnu dot org 2006-03-01 13:15 ` h dot m dot brand at xs4all dot nl 2006-03-01 13:45 ` h dot m dot brand at xs4all dot nl 2006-03-01 14:37 ` pinskia at gcc dot gnu dot org 2006-03-01 15:01 ` h dot m dot brand at xs4all dot nl 2006-03-01 15:21 ` h dot m dot brand at xs4all dot nl 2006-03-01 15:54 ` h dot m dot brand at xs4all dot nl 2006-03-02 17:47 ` steven at gcc dot gnu dot org 2006-03-05 15:51 ` pinskia at gcc dot gnu dot org 2006-03-05 16:46 ` h dot m dot brand at xs4all dot nl [this message] 2006-03-11 15:14 ` danglin at gcc dot gnu dot org 2006-03-11 17:12 ` h dot m dot brand at xs4all dot nl 2006-03-11 19:00 ` h dot m dot brand at xs4all dot nl 2006-03-11 23:57 ` dave at hiauly1 dot hia dot nrc dot ca 2006-03-12 0:29 ` dave at hiauly1 dot hia dot nrc dot ca 2006-03-12 12:26 ` h dot m dot brand at xs4all dot nl 2006-03-12 22:05 ` dave at hiauly1 dot hia dot nrc dot ca 2006-03-13 18:03 ` h dot m dot brand at xs4all dot nl 2006-03-13 18:10 ` dave at hiauly1 dot hia dot nrc dot ca 2006-03-23 17:49 ` dave at hiauly1 dot hia dot nrc dot ca 2006-03-23 18:11 ` h dot m dot brand at xs4all dot nl 2006-04-09 18:32 ` danglin at gcc dot gnu dot org 2006-04-09 18:56 ` danglin at gcc dot gnu dot org 2006-04-09 20:39 ` danglin at gcc dot 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=20060305164604.13333.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: linkBe 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).