public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/19797] [4.0 Regression] g++.dg/abi/inline1.C fails on hppa*-*-hpux* Date: Fri, 25 Feb 2005 08:27:00 -0000 [thread overview] Message-ID: <20050224234952.9463.qmail@sourceware.org> (raw) In-Reply-To: <20050207000300.19797.jsm28@gcc.gnu.org> ------- Additional Comments From jsm28 at gcc dot gnu dot org 2005-02-24 23:49 ------- Even with the patch 2005-02-20 John David Anglin <dave.anglin@nrc-cnrc.gc.ca> * pa.c (pa_assemble_integer, get_plabel): Small cleanups. (pa_asm_output_mi_thunk): Use asm_output_insn instead of fprintf. * som.h (ASM_OUTPUT_EXTERNAL_LIBCALL): Small cleanup. present in the tree, I still get a linker crash on hppa2.0w-hp-hpux11.11 with my patch as attached to this PR. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19797
next prev parent reply other threads:[~2005-02-24 23:49 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-07 6:03 [Bug c++/19797] New: " jsm28 at gcc dot gnu dot org 2005-02-07 13:06 ` [Bug c++/19797] " pinskia at gcc dot gnu dot org 2005-02-13 2:12 ` jsm28 at gcc dot gnu dot org 2005-02-13 5:07 ` pinskia at gcc dot gnu dot org 2005-02-13 17:25 ` danglin at gcc dot gnu dot org 2005-02-13 17:41 ` danglin at gcc dot gnu dot org 2005-02-13 17:58 ` danglin at gcc dot gnu dot org 2005-02-13 17:58 ` joseph at codesourcery dot com 2005-02-13 18:00 ` joseph at codesourcery dot com 2005-02-13 18:04 ` dave at hiauly1 dot hia dot nrc dot ca 2005-02-15 15:55 ` dave at hiauly1 dot hia dot nrc dot ca 2005-02-21 0:35 ` pinskia at gcc dot gnu dot org 2005-02-25 8:27 ` jsm28 at gcc dot gnu dot org [this message] 2005-02-25 15:35 ` dave at hiauly1 dot hia dot nrc dot ca 2005-03-05 1:41 ` [Bug c++/19797] [4.0/4.1 " cvs-commit at gcc dot gnu dot org 2005-03-05 1:59 ` cvs-commit at gcc dot gnu dot org 2005-03-05 3:14 ` 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=20050224234952.9463.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).