From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 55378 invoked by alias); 14 Oct 2015 08:48:54 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 55354 invoked by uid 48); 14 Oct 2015 08:48:50 -0000 From: "other+gcc at meresinski dot eu" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67961] New: Incorrect type of meber of struct in error message Date: Wed, 14 Oct 2015 08:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 5.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: other+gcc at meresinski dot eu X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-10/txt/msg01076.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D67961 Bug ID: 67961 Summary: Incorrect type of meber of struct in error message Product: gcc Version: 5.2.0 Status: UNCONFIRMED Severity: minor Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: other+gcc at meresinski dot eu Target Milestone: --- Created attachment 36506 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D36506&action=3Dedit Test case Compiling following code produces incorrect error message: #include void foo(std::size_t &f) { f =3D 5; } struct A { uint32_t val; }; int main() { A a, *aptr =3D &a; foo(aptr->val); return 0; } g++ --std=3Dc++11 foo.cpp gives error message: error: invalid initialization of non-const reference of type =E2=80=98std::= size_t& {aka long unsigned int&}=E2=80=99 from an rvalue of type =E2=80=98std::size_t {a= ka long unsigned int}=E2=80=99 foo(aptr->val); ^ where type of that rvalue variable is uint32_t not std::size_t. I think I should add that system is 64bit so std::size_t has 64 bits. >>From gcc-bugs-return-499522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Oct 14 09:37:24 2015 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 24867 invoked by alias); 14 Oct 2015 09:37:24 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 24804 invoked by uid 48); 14 Oct 2015 09:37:19 -0000 From: "ienkovich at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/67920] [6 Regression] wrong code with -O3 Date: Wed, 14 Oct 2015 09:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: ienkovich at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 6.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-10/txt/msg01077.txt.bz2 Content-length: 507 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67920 Ilya Enkovich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |FIXED --- Comment #10 from Ilya Enkovich --- (In reply to James Almer from comment #9) > Looks like it did. Thanks. Fixed then