public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/38172]  New: warn_unused_result does not work with structs not containing a copy constructor
Date: Tue, 18 Nov 2008 22:14:00 -0000	[thread overview]
Message-ID: <bug-38172-6528@http.gcc.gnu.org/bugzilla/> (raw)

Take:
struct MyClass
{
};

typedef struct MyClass MyClass;

int Bar1( void ) __attribute__((warn_unused_result)) __attribute__((noinline));
MyClass Bar2( void ) __attribute__((warn_unused_result))
__attribute__((noinline));

int Bar1( void )
{
    return 0;
}

MyClass Bar2( void )
{
}

void Foo( void )
{
    Bar1(); // Warns
    Bar2(); // Does not warn
}
--- CUT ---
In Foo, Bar1 and Bar2 should cause a warning, only Bar1 causes a warning with
the C++ front-end.  While both cause a warning to show up with the C front-end.


-- 
           Summary: warn_unused_result does not work with structs not
                    containing a copy constructor
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Keywords: diagnostic
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pinskia at gcc dot gnu dot org


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


             reply	other threads:[~2008-11-18 22:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-18 22:14 pinskia at gcc dot gnu dot org [this message]
2008-11-18 22:16 ` [Bug c++/38172] " pinskia at gcc dot gnu dot org
2008-11-18 22:17 ` pinskia 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=bug-38172-6528@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).