mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jens Gustedt <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: Re: Does musl build error with gcc-4.9.2+ git repo resolved
Date: Wed, 11 Mar 2015 13:18:46 +0100	[thread overview]
Message-ID: <1426076326.26518.10.camel@inria.fr> (raw)
In-Reply-To: <20150311120200.GD23507@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 1955 bytes --]

Am Mittwoch, den 11.03.2015, 08:02 -0400 schrieb Rich Felker:
> On Wed, Mar 11, 2015 at 09:52:35AM +0530, vlse wrote:
> > I want to know whether the gcc 4.9.x bug bugzilla id 61144 resolved
> > with latest git/svn branch of gcc-4.9.x.
> > 
> > That bugzilla page says bug 61144 has been resolved. Anybody has
> > confirmed it? Has musl changed it's build scripts to account that?
> 
> I haven't done detailed tests to confirm, but I believe the bug is
> fixed in 4.9.2. However there's another very serious bug that affects
> 4.9.2 and possibly all 4.9.x releases causing incorrect code gen:
> 
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65307
> 
> On the musl side, we worked aroung bug 61144 with gratuitous use of
> volatile before 4.9.2 was released. This workaround might be reverted
> at some point in the future if the affected versions are deemed too
> buggy for any distros to keep them around.

I have another bug in 4.9 that is really nasty and for which the
minimal code to produce is very lengthy and contrived. So much that I
didn't even yet reported it because I wanted to cook it down a bit,
still. For the moment it involves at least 15 levels of nested for
loops and setjmp/longjmp. The bug then has the compiler crash, but who
knows what it produces if it doesn't crash for code that is more
normal.

There are other issues (but perhaps related) that are really
suspicious with that line of gcc. The static analyser seems to be
screwed and tells me about lack of initialization for variables that
are initialized.

So I wouldn't trust 4.9 one bit for anything related to production.

Jens

-- 
:: INRIA Nancy Grand Est ::: Camus ::::::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::




[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2015-03-11 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11  4:22 vlse
2015-03-11  6:23 ` Timo Teras
2015-03-11 12:02 ` Rich Felker
2015-03-11 12:18   ` Jens Gustedt [this message]

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=1426076326.26518.10.camel@inria.fr \
    --to=jens.gustedt@inria.fr \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).