public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/51011] FAIL: gcc.dg/atomic-generic.c (test for excess errors) Date: Mon, 07 Nov 2011 19:30:00 -0000 [thread overview] Message-ID: <bug-51011-4-pXLoZZHFGf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51011-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51011 Andrew Macleod <amacleod at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amacleod at redhat dot com --- Comment #1 from Andrew Macleod <amacleod at redhat dot com> 2011-11-07 19:27:36 UTC --- Is dejagnu on hpux limited somehow? atomic-generic.c for instance has the line: /* { dg-additional-sources "atomic-generic-aux.c" } */ which on all the targets I have tried it on cause atomic-generic-aux.c to be compiled at the same time as atomic-generic.c, and it supplies those functions... is there a reason that doesn't happen on hpux?
next prev parent reply other threads:[~2011-11-07 19:28 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-07 19:25 [Bug other/51011] New: " danglin at gcc dot gnu.org 2011-11-07 19:30 ` amacleod at redhat dot com [this message] 2011-11-07 20:42 ` [Bug other/51011] " dave.anglin at bell dot net 2011-11-08 0:13 ` dave.anglin at bell dot net 2011-11-08 3:57 ` amacleod at redhat dot com 2011-11-08 14:58 ` dave.anglin at bell dot net 2011-11-16 19:20 ` amacleod at redhat dot com 2011-11-17 2:27 ` dave.anglin at bell dot net 2011-11-17 21:55 ` amacleod at redhat dot com 2011-11-17 23:36 ` dave.anglin at bell dot net 2011-11-18 13:45 ` dave.anglin at bell dot net 2011-11-25 14:07 ` amacleod at redhat dot com 2012-01-23 2:39 ` amacleod at redhat dot com 2012-01-23 13:32 ` danglin at gcc dot gnu.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=bug-51011-4-pXLoZZHFGf@http.gcc.gnu.org/bugzilla/ \ --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).