All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] gcc: Enable __cxa_atexit for final GCC
Date: Mon, 21 Jan 2019 21:51:47 +0100	[thread overview]
Message-ID: <20190121215147.6c732fac@gmx.net> (raw)
In-Reply-To: <CAOMZO5Cr-N8guA2hE-PjsOm4uDj67cnmNroKjMvykPZVS2dwbQ@mail.gmail.com>

Hello *,

On Mon, 21 Jan 2019 13:04:46 -0200, Fabio Estevam <festevam@gmail.com> wrote:

> Hi Peter,
> 
> On Thu, Nov 29, 2018 at 7:15 PM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> >
> > Hello,
> >
> > On Fri, 16 Nov 2018 14:26:18 +0300, Alexey Brodkin wrote:  
> > > This is what GCC manual says [1]:  
> > > -------------------------->8----------------------  
> > > --enable-__cxa_atexit  
> >
> > I've applied to next, but after dropping the "for final GCC" from the
> > commit title, since cxa_atexit is now used for both the initial gcc and
> > the final gcc.  
> 
> Could this one be applied to Buildroot stable?

+1

> 
> The lack of this patch causes is causing issues on Mesa:
> https://www.mail-archive.com/mesa-dev at lists.freedesktop.org/msg212440.html

Did re-run the same buildroot-2018.11/mesa/etnaviv test, could confirm enabling
__cxa_atexit fixes the mesa double-free on exit...

Regards,
Peter
  
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2019-01-21 20:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 11:26 [Buildroot] [PATCH v2] gcc: Enable __cxa_atexit for final GCC Alexey Brodkin
2018-11-29 21:14 ` Thomas Petazzoni
2019-01-21 15:04   ` Fabio Estevam
2019-01-21 20:51     ` Peter Seiderer [this message]
2019-02-24 21:20     ` Peter Korsgaard

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=20190121215147.6c732fac@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.