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
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
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 {
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