public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/51934] FAIL: g++.dg/torture/pr51344.C  -O0  (test for excess errors) on powerpc*-*-*
Date: Sun, 22 Jan 2012 00:54:00 -0000	[thread overview]
Message-ID: <bug-51934-4-vhZEeEshdk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51934-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51934

--- Comment #8 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-01-21 23:58:19 UTC ---
> You mean errors out?  format attribute must have 3 arguments.
> Try leaf, or nothrow etc. attributes instead, format is a bad idea for a method
> that isn't printf/scanf like.

Well, format was the first attribute I have found with your requirements:
common to all platforms, hangs before the commit and passes after it (aligned,
cold, flatten, malloc, noclone, noinline,  nothrow, pure don't work; ifunc ,
no_instrument_function, noreturn, no_split_stack give warnings or errors).
nonnull meets also the above criteria, but is also supposed to use arguments.
If someone has more patience than me, be my guest!

Now if its use without arguments should yields an error, it is another bug.


  parent reply	other threads:[~2012-01-21 23:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21 16:11 [Bug target/51934] New: " dominiq at lps dot ens.fr
2012-01-21 16:16 ` [Bug target/51934] " mikpe at it dot uu.se
2012-01-21 17:32 ` dominiq at lps dot ens.fr
2012-01-21 21:31 ` mikpe at it dot uu.se
2012-01-21 22:32 ` dominiq at lps dot ens.fr
2012-01-21 22:54 ` jakub at gcc dot gnu.org
2012-01-21 23:43 ` dominiq at lps dot ens.fr
2012-01-21 23:58 ` jakub at gcc dot gnu.org
2012-01-22  0:54 ` dominiq at lps dot ens.fr [this message]
2012-01-23 12:52 ` dominiq at lps dot ens.fr
2012-01-23 12:55 ` [Bug target/51934] FAIL: g++.dg/torture/pr51344.C -O0 (test for excess errors) due to "cdecl attribute ignored" warning dominiq at lps dot ens.fr
2012-01-23 14:55 ` jason at gcc dot gnu.org
2012-01-23 14:58 ` jason at gcc dot gnu.org
2012-01-23 15:06 ` dominiq at lps dot ens.fr
2012-01-23 15:20 ` jakub at gcc dot gnu.org
2012-01-23 15:27 ` dominiq at lps dot ens.fr
2012-01-23 15:51 ` jason at gcc dot gnu.org
2012-01-23 16:09 ` dominiq at lps dot ens.fr
2012-01-23 16:36 ` jakub at gcc dot gnu.org
2012-01-23 22:47 ` dominiq at lps dot ens.fr
2012-01-24  6:06 ` jason at gcc dot gnu.org
2012-01-25 15:16 ` danglin at gcc dot gnu.org
2012-01-25 17:24 ` jason at gcc dot gnu.org
2012-01-25 19:27 ` danglin at gcc dot gnu.org
2012-03-06  8:28 ` jakub at gcc dot gnu.org
2012-03-06  8:31 ` jakub 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-51934-4-vhZEeEshdk@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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).