mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Alba Pompeo <albapompeo@gmail.com>, musl@lists.openwall.com
Subject: Re: Re: Julia on musl libc systems
Date: Sun, 31 Jan 2016 13:45:50 -0500	[thread overview]
Message-ID: <20160131184546.GG9349@brightrain.aerifal.cx> (raw)
In-Reply-To: <20160131180034.GZ9621@port70.net>

On Sun, Jan 31, 2016 at 07:00:34PM +0100, Szabolcs Nagy wrote:
> * Szabolcs Nagy <nsz@port70.net> [2016-01-31 17:49:56 +0100]:
> > * Alba Pompeo <albapompeo@gmail.com> [2016-01-30 23:13:48 -0200]:
> > > It's one of musl dependencies (suitesparse).
> > > It's an off-putting issue, but I hope it's fixable. An internal compiler error.
> > > https://github.com/tkelman/julia-alpine/issues/1#issuecomment-177282137
> > > The .c file in question is here.
> > > https://github.com/jluttine/suitesparse/blob/master/CHOLMOD/Modify/t_cholmod_updown_numkr.c
> > > 
> > 
> > if an unstable version of the clang preprocessor crashes
> > with ice, it is probably not libc related.
> > 
> 
> sorry, i misunderstood the discussion
> 
> i see it is the alpine gcc that crashed on SuiteSparse
> and i can reproduce it

Are they perhaps using C++ and precompiled headers? The latter are
silently broken if gcc is built as pie (Alpine builds everything as
pie) and will crash the compiler. If this is the issue, the right fix
is to patch gcc to ignore precompiled headers and always use the
original source ones, but upstream gcc trunk (gcc6) has a (somewhat
buggy) patch to force-disable pie in its build.

Rich


  reply	other threads:[~2016-01-31 18:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJDAfTAwqGWWn3hx8k4jbynAgsy=Q8GHmccOod-xmZ87327z+A@mail.gmail.com>
     [not found] ` <20160130130956.GR9621@port70.net>
     [not found]   ` <CAJDAfTAyYz8Xnwv3Xj_qTxM_AErVjfRUPymffExTZ4KN-_eV5g@mail.gmail.com>
     [not found]     ` <20160130144011.GS9621@port70.net>
     [not found]       ` <CAJDAfTAkMDEc4s2tZQJPW0WDhvSCfgNGDEVPAh+Xd+5YB4_K4Q@mail.gmail.com>
     [not found]         ` <CAJDAfTASp=MXYur_pdA-MWS6LJThEgXa2wtGSDc+kE4kiYHyjA@mail.gmail.com>
     [not found]           ` <20160131010750.GT9621@port70.net>
     [not found]             ` <CAJDAfTBZHQ-3pEH4MA0epo_RTTajbV4ohZC06WohaffkLYeW3Q@mail.gmail.com>
2016-01-31 16:49               ` Szabolcs Nagy
2016-01-31 18:00                 ` Szabolcs Nagy
2016-01-31 18:45                   ` Rich Felker [this message]
2016-01-31 20:40                     ` Szabolcs Nagy
2016-01-31 20:42                       ` Szabolcs Nagy
2016-05-21 13:37                         ` Alba Pompeo
2016-06-08 22:00                           ` Alba Pompeo
2016-06-29 17:03                             ` Alexander Monakov
2016-07-12 22:47                               ` Alba Pompeo

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=20160131184546.GG9349@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=albapompeo@gmail.com \
    --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).