public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dirkneukirchen at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61785] New: Sigsegv with enabled optimize -Os , -O2 in sample_format_size
Date: Fri, 11 Jul 2014 22:42:00 -0000 [thread overview]
Message-ID: <bug-61785-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61785
Bug ID: 61785
Summary: Sigsegv with enabled optimize -Os , -O2 in
sample_format_size
Product: gcc
Version: 4.8.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: dirkneukirchen at web dot de
Created attachment 33109
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33109&action=edit
i486-openwrt-linux-g++ -v output
I get a SIGSEGV when running the binary compiled with default switches
(containing -Os) in qemu.
If I compile with -O0 the program is working.
GCC 4.6.4 is generating working code with -Os
4.8.0, 4.8.3, 4.9.0 do not work with -Os ; -O0 binaries work
Source is from mpd 0.18.11
gcc is used in OpenWrt buildroot to compile it for target arch (x86)
I opened a ticket on mpd bugtracker, provided gdb output and was told it's a
compiler bug - thats why I opened a ticket here.
the mpd bugtracker ticket is: http://bugs.musicpd.org/view.php?id=4024
First time reporter.
next reply other threads:[~2014-07-11 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 22:42 dirkneukirchen at web dot de [this message]
2014-07-11 22:44 ` [Bug c++/61785] " dirkneukirchen at web dot de
2014-07-11 23:00 ` dirkneukirchen at web dot de
2014-07-13 3:29 ` andi-gcc at firstfloor dot org
2021-07-22 18:57 ` [Bug middle-end/61785] " pinskia at gcc dot gnu.org
2024-03-12 22:30 ` pinskia 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-61785-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).