public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64798] [5 regression] g++.old-deja/g++.eh/badalloc1.C FAILs
Date: Mon, 26 Jan 2015 15:00:00 -0000	[thread overview]
Message-ID: <bug-64798-4-rEpHivjPSu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64798-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64798

--- Comment #1 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 26 Jan 2015, ro at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64798
> 
>             Bug ID: 64798
>            Summary: [5 regression] g++.old-deja/g++.eh/badalloc1.C FAILs
>            Product: gcc
>            Version: 5.0
>             Status: UNCONFIRMED
>           Severity: normal
>           Priority: P3
>          Component: libstdc++
>           Assignee: unassigned at gcc dot gnu.org
>           Reporter: ro at gcc dot gnu.org
>                 CC: rguenth at gcc dot gnu.org
>               Host: sparc*-sun-solaris2.*
>             Target: sparc*-sun-solaris2.*
>              Build: sparc*-sun-solaris2.*
> 
> Between 20150116 (r219745) and 20150123 (r220039),
> g++.old-deja/g++.eh/badalloc1.C
> started to FAIL on 32-bit Solaris/SPARC:
> 
> FAIL: g++.old-deja/g++.eh/badalloc1.C  -std=c++11 execution test
> FAIL: g++.old-deja/g++.eh/badalloc1.C  -std=c++14 execution test
> FAIL: g++.old-deja/g++.eh/badalloc1.C  -std=c++98 execution test
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1 (LWP 1)]
> __cxxabiv1::__cxa_throw (obj=0x2195c <arena+92>, 
>     tinfo=0x73908 <typeinfo for int>, dest=0x0)
>     at /vol/gcc/src/hg/trunk/local/libstdc++-v3/libsupc++/eh_throw.cc:76
> 76       
> __GXX_INIT_PRIMARY_EXCEPTION_CLASS(header->exc.unwindHeader.exception_class);
> 1: x/i $pc
> => 0xff220314 <__cxxabiv1::__cxa_throw(void*, std::type_info*, void
> (*)(void*))+96>:    sttw  %g2, [ %i0 + -24 ]
> (gdb) where
> #0  __cxxabiv1::__cxa_throw (obj=0x2195c <arena+92>, 
>     tinfo=0x73908 <typeinfo for int>, dest=0x0)
>     at /vol/gcc/src/hg/trunk/local/libstdc++-v3/libsupc++/eh_throw.cc:76
> #1  0x00011114 in fn_throw ()
>     at
> /vol/gcc/src/hg/trunk/local/gcc/testsuite/g++.old-deja/g++.eh/badalloc1.C:98
> #2  0x000112f8 in main ()
>     at
> /vol/gcc/src/hg/trunk/local/gcc/testsuite/g++.old-deja/g++.eh/badalloc1.C:129
> (gdb) p $i0-24
> $3 = 137540
> 
> The SEGV happens because the sttw target needs to be 8-byte aligned, but is
> not.

Does malloc return 8-byte aligned memory?  Is __alignof__

      struct free_entry {
        std::size_t size;
        free_entry *next;
      };

less than 8?

Thanks,
Richard.


  parent reply	other threads:[~2015-01-26 15:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 13:52 [Bug libstdc++/64798] New: " ro at gcc dot gnu.org
2015-01-26 13:53 ` [Bug libstdc++/64798] " ro at gcc dot gnu.org
2015-01-26 15:00 ` rguenther at suse dot de [this message]
2015-01-26 15:02 ` rguenther at suse dot de
2015-01-26 15:23 ` rguenth at gcc dot gnu.org
2015-01-26 15:45 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-01-27 10:58 ` rguenth at gcc dot gnu.org
2015-01-27 12:10 ` jakub at gcc dot gnu.org
2015-01-27 12:16 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-01-27 12:27 ` rguenther at suse dot de
2015-01-27 12:31 ` rguenth at gcc dot gnu.org
2015-01-27 12:33 ` jakub at gcc dot gnu.org
2015-01-27 12:38 ` rguenther at suse dot de
2015-01-27 12:40 ` rguenth at gcc dot gnu.org
2015-01-27 12:42 ` jakub at gcc dot gnu.org
2015-01-27 12:51 ` rguenther at suse dot de
2015-01-27 12:52 ` jakub at gcc dot gnu.org
2015-01-28  9:54 ` rguenth at gcc dot gnu.org
2015-01-28 10:01 ` rguenth 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-64798-4-rEpHivjPSu@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).