Re: [C PATCH] Fix PR86125 fallout

2019-01-28 Thread Joseph Myers
On Sat, 26 Jan 2019, Jakub Jelinek wrote: > Hi! > > Here is an untested patch that should fix all of that, ok for trunk > if it passes bootstrap/regtest on {x86_64,i686}-linux? OK. -- Joseph S. Myers jos...@codesourcery.com

Re: [C PATCH] Fix PR86125 fallout

2019-01-27 Thread Christophe Lyon
On Sat, 26 Jan 2019 at 23:53, Jakub Jelinek wrote: > > On Sat, Jan 26, 2019 at 04:01:13PM +0100, Jakub Jelinek wrote: > > Here is an untested patch that should fix all of that, ok for trunk > > if it passes bootstrap/regtest on {x86_64,i686}-linux? > > Had to change: > -+ { dg-do compile { targe

Re: [C PATCH] Fix PR86125 fallout

2019-01-26 Thread Jakub Jelinek
On Sat, Jan 26, 2019 at 04:01:13PM +0100, Jakub Jelinek wrote: > Here is an untested patch that should fix all of that, ok for trunk > if it passes bootstrap/regtest on {x86_64,i686}-linux? Had to change: -+ { dg-do compile { target { lp64 || ilp32 || llp64 } } } ++ { dg-do compile { target {

[C PATCH] Fix PR86125 fallout

2019-01-26 Thread Jakub Jelinek
Hi! Here is an untested patch that should fix all of that, ok for trunk if it passes bootstrap/regtest on {x86_64,i686}-linux? Notes: 1) seems the C++ FE is even stricter and uses the builtin_structptr_types[x].str string to verify the pointed type has the right TYPE_NAME; is that something