public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: t.artem@mailcity.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/10015: gcc++ 3.2.2 can create buggy binaries with -Os option set
Date: Mon, 10 Mar 2003 12:26:00 -0000	[thread overview]
Message-ID: <20030310122000.13839.qmail@sources.redhat.com> (raw)


>Number:         10015
>Category:       c++
>Synopsis:       gcc++ 3.2.2 can create buggy binaries with -Os option set
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 10 12:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     t.artem@mailcity.com
>Release:        gcc 3.2.2
>Organization:
>Environment:
RedHat Linux 7.3: glibc 2.2.5, gcc-3.2.2
>Description:
Compiling qt-x11-free library 3.1.1 and then KDE 3.1 libraries with -Os flag produces _very_ buggy binaries (especially KDE ones as well as qtconfig and uic programs). Those binaries segfault at _every_ program exit
>How-To-Repeat:
Compile qt library (3.1.1) with -Os flag (instead of default -O2) - go to qt_src_dir/mkspecs/linux-g++ to do it and then KDE-libs and KDE-base (3.1) - and you've got buggy binaries
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-03-10 12:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030310122000.13839.qmail@sources.redhat.com \
    --to=t.artem@mailcity.com \
    --cc=gcc-gnats@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).