public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pavel.zbitskiy at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55988] New: Incorrect code generation with const and -std=c++0x
Date: Tue, 15 Jan 2013 08:02:00 -0000	[thread overview]
Message-ID: <bug-55988-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55988
           Summary: Incorrect code generation with const and -std=c++0x
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: pavel.zbitskiy@gmail.com


Created attachment 29167
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29167
the preprocessed file

The following code
/* ---------- */
class Base
{
public:
    virtual void execute() const = 0;
    virtual ~Base() {}
};

class Pop : public Base
{
public:
    virtual void execute() const { return; }
};

const Pop pop;

int main()
{
    pop.execute();
    return 0;
}
/* ---------- */

will be crashed if source is compiled with -std=c++0x (g++ -Wall -Wextra
-std=c++0x const-0x.cpp -o const-0x).

This happens because variable pop is located in read-only memory
080487f8 l     O .rodata        00000004              _ZL3pop

and Pop::~Pop() has the following code
   0x080486ba <+6>:    mov    eax,DWORD PTR [ebp+0x8]
=> 0x080486bd <+9>:    mov    DWORD PTR [eax],0x80487b0
   0x080486c3 <+15>:    mov    eax,DWORD PTR [ebp+0x8]
(gdb) info registers eax
eax            0x80487f8

In other words it tries to write to read-only location.

For more complicated programs the following code was generated in destructor:
   0xb7b66b34 <+20>: mov eax,DWORD PTR [esp+0x4]
=> 0xb7b66b38 <+24>: mov DWORD PTR [eax],edx
   0xb7b66b3a <+26>: ret
with the same consequences.

System information:
Linux laptop-1 3.5.0-21-generic #32-Ubuntu SMP Tue Dec 11 18:52:46 UTC 2012
i686 i686 i686 GNU/Linux

g++ -v output:
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.7/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
4.7.2-2ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs
--enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.7 --enable-shared --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object
--enable-plugin --enable-objc-gc --enable-targets=all --disable-werror
--with-arch-32=i686 --with-tune=generic --enable-checking=release
--build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu
Thread model: posix
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)


             reply	other threads:[~2013-01-15  8:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15  8:02 pavel.zbitskiy at gmail dot com [this message]
2013-01-15  8:41 ` [Bug c++/55988] " 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-55988-4@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).