[Bug c++/40202] warning about passing non-POD objects through �...� should include name and location of declaration being called

[Bug c++/40202] warning about passing non-POD objects through �...� should include name and location of declaration being called

[paolo.carlini at oracle dot com]

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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #4 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-09-29 16:03:15 UTC ---
Manuel, do you have an opinion about this rather old issue? In the meanwhile,
the warning became an hard error, when it applies. Thus the original testcase
is just accepted, and this variant:

void f(...);

struct X {
  X();
  X(const X&);
};

void g() {
    X x;
    f(x);
}

gives:

40202.C: In function ‘void g()’:
40202.C:10:8: error: cannot pass objects of non-trivially-copyable type ‘struct
X’ through ‘...’

ICC warns exactly at the same line, 10, and nothing else.

[Bug c++/40202] warning about passing non-POD objects through �...� should include name and location of declaration being called

[redi at gcc dot gnu.org]

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

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-09-29 16:16:48 UTC ---
(In reply to comment #4)
> In the meanwhile,
> the warning became an hard error, when it applies.

It went from "undefined" to "conditionally-supported" behaviour in C++11

> ICC warns exactly at the same line, 10, and nothing else.

Clang too.

[Bug c++/40202] warning about passing non-POD objects through �...� should include name and location of declaration being called

[paolo.carlini at oracle dot com]

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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|gcc-bugs at gcc dot gnu.org |

--- Comment #6 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-09-29 17:14:56 UTC ---
Thanks Jon for the clarification about C++11. Thus, let's wait a bit more in
case Manuel has further comments, otherwise, let's just close this.

[Bug c++/40202] warning about passing non-POD objects through �...� should include name and location of declaration being called

[redi at gcc dot gnu.org]

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

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-09-29 17:26:57 UTC ---
To the OP, you've probably fixed it by now, but you must have a varargs
function with ... somewhere, or you wouldn't get the error. You could add a
conflicting declaration which would make the compiler tell you the location.

void f(...);

struct X {
    X();
};

struct Unique;
Unique* f(...);

void g() {
    X x;
    f(x);
}

t.cc:8: error: new declaration 'Unique* f(...)'
t.cc:1: error: ambiguates old declaration 'void f(...)'

Now you know where your mystery f(...) came from.

[Bug c++/40202] warning about passing non-POD objects through �...� should include name and location of declaration being called

[manu at gcc dot gnu.org]

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

--- Comment #8 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2011-09-29 20:54:46 UTC ---
(In reply to comment #4)
> Manuel, do you have an opinion about this rather old issue? In the meanwhile,
> the warning became an hard error, when it applies. Thus the original testcase
> is just accepted, and this variant:

Paolo, thanks for asking my opinion! As a user, I would appreciate an extra
inform saying where the variadic function is declared, like g++ does for other
diagnostics. But since I don't know how hard is to get that location at the
error point, and I am not volunteering to do the work...

BTW, I think it is great that you are triaging and fixing so many C++
diagnostic bugs, it was sorely needed.

[Bug c++/40202] warning about passing non-POD objects through �...� should include name and location of declaration being called

[paolo.carlini at oracle dot com]

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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #9 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-09-29 21:08:12 UTC ---
You are welcome ;) I'm sure the diagnostics could be improved, in this case
too, but given that we do behave exactly like the two other top class
front-ends, and also given the amount of work required to make progress on
other issues, I'm glad you agree we can consider the current status good
enough.

[Bug c++/40202] warning about passing non-POD objects through ‘...’ should include name and location of declaration being called

[pinskia at gcc dot gnu dot org]

------- Comment #1 from pinskia at gcc dot gnu dot org  2009-05-19 22:04 -------
So are you asking to print out 'x' here? 


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
           Keywords|                            |diagnostic


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