On Sun, 12 May 2019, Marc Glisse wrote:
this patch lets gcc know that if a pointer existed before the call to malloc,
the result of malloc cannot alias it. This is a bit ad hoc and fragile. A
small improvement would be, when the 2 statements are in the same bb but in
the wrong order, to check
It seems to be quite frequently the case that we need to look at the
pro/epilogue behaviour.
This adds the state of the “save_world” computation to the debug output that’s
printed in
response to -mdebug=stack on powerpc-darwin.
tested on powerpc-darwin9, applied to trunk.
thanks
Iain
gcc/
Hello,
this patch lets gcc know that if a pointer existed before the call to
malloc, the result of malloc cannot alias it. This is a bit ad hoc and
fragile. A small improvement would be, when the 2 statements are in the
same bb but in the wrong order, to check if there is any statement in
On Sun, May 12, 2019 at 12:47:04AM +0300, Janne Blomqvist wrote:
> When generating C prototypes for Fortran procedures with the
> -fc-prototypes and -fc-prototypes-external options, print a snippet
> defining macros for complex types, and add C++ support by suppressing
> mangling.
>
>
When generating C prototypes for Fortran procedures with the
-fc-prototypes and -fc-prototypes-external options, print a snippet
defining macros for complex types, and add C++ support by suppressing
mangling.
fortran/ChangeLog:
2019-05-12 Janne Blomqvist
* dump-parse-tree.c
On 25.04.19 22:07, Andreas Tobler wrote:
On 18.03.19 22:28, Andreas Tobler wrote:
On 18.03.19 22:22, Jeff Law wrote:
On 3/17/19 2:40 PM, Andreas Tobler wrote:
Hi all,
this patch adds support for multilib on x86_64-unknown-freebsd*
The multilibs are 32-bit.
This patch is functionality tested
On 25.04.19 22:07, Andreas Tobler wrote:
On 18.03.19 22:28, Andreas Tobler wrote:
On 18.03.19 22:22, Jeff Law wrote:
On 3/17/19 2:40 PM, Andreas Tobler wrote:
Hi all,
this patch adds support for multilib on x86_64-unknown-freebsd*
The multilibs are 32-bit.
This patch is functionality tested
This does not alter the fixincludes, but only the test conditions - the test
was failing because test_text should not be provided for wrap fixes.
Tested on x86-64-linux and x86-64-darwin (also confirmed to fix the issue by
the OP).
Applied to trunk, backport to 9 in due course.
Thanks
Iain
The Profile Mode extension is not used by anybody, nor maintained by
anybody. The containers do not support the full API specified in recent
standards, and so enabling Profile Mode is not source compatible with
much modern C++ code. The heuristics that would check the profile
information and make
This type is not a conforming allocator, because it cannot be reliably
rebound to allocate for a different type. The result of the rebind
transformation still uses the same underlying std::tr1::array
array, which may not be correctly aligned or even have elements the
right size for the value_type
On Sat, May 11, 2019 at 09:38:22AM +0100, Richard Sandiford wrote:
> Jakub Jelinek writes:
> > Previously, the mere existence of the addressable variables this_context
> > and cur_context prevented tail call on the early out
> > return _Unwind_RaiseException (exc);
> > but since r271013 the
The tests fail as noted in the PR, because Darwin’s ABI mandates indirection
for common accesses, which means that the codegen doesn’t match what the tests
expect.
In this case, we can fix this simply by placing the relevant vars in the
regular data section (by appending -fno-common to the
> Le 11 mai 2019 à 15:49, Thomas Koenig a écrit :
>
> Hi Dominique,
>
>> How ever adding the new tests is a real PITA!-(
>> Could you improve the naming scheme for them
>
> What should be the preferrred naming scheme for a
> test that is split? I'm open to suggestions (but also,
> the
Hi Dominique,
How ever adding the new tests is a real PITA!-(
Could you improve the naming scheme for them
What should be the preferrred naming scheme for a
test that is split? I'm open to suggestions (but also,
the naming convention should not matter once the test
cases are committed).
Hi Thomas,
I confirm that the new patch fixes the ICE.
How ever adding the new tests is a real PITA!-(
Could you improve the naming scheme for them
TIA
Dominique
On 5/10/19 3:59 PM, Jonathan Wakely wrote:
On 10/05/19 14:40 +0100, Jonathan Wakely wrote:
On Thu, 9 May 2019 at 06:49, François Dumont wrote:
Hi
Patch similar to the one I just apply for deque iterator including
NRVO copy ellision fix.
* include/bits/stl_bvector.h
Hello world,
this new version of the inlie argument packing patch (PR 88821)
avoids the ICE on the test case for PR 61968. Otherwise it is
unchanged.
Regression-tested. OK for trunk?
Regards
Thomas
2019-05-11 Thomas Koenig
PR fortran/88821
* expr.c
Jakub Jelinek writes:
> Hi!
>
> My recent patch for tail call improvement apparently affects also the
> _Unwind_Resume_or_Rethrow function in libgcc:
>
> _Unwind_Reason_Code __attribute__((optimize ("no-omit-frame-pointer")))
> _Unwind_Resume_or_Rethrow (struct _Unwind_Exception *exc)
> {
>
We can use pinsrd when moving DImode value from integer register pair
to xmm reg for 32bit SSE4.1 targets.
2019-05-11 Uroš Bizjak
* config/i386/i386.md (floatdi2_i387_with_xmm):
Use pinsrd for TARGET_SSE4_1.
* config/i386/sse.md (movdi_to_sse): Ditto.
Bootstrapped and regression
Committed to 9-branch as revision 271089.
Paul
On Fri, 10 May 2019 at 09:00, Paul Richard Thomas
wrote:
>
> Committed to trunk as revision 271057.
>
> Will do likewise with 9-branch asap.
>
> Cheers
>
> Paul
>
> On Wed, 8 May 2019 at 19:40, Paul Richard Thomas
> wrote:
> >
> > Unless there are
On Thu, 2 May 2019, Thomas Schwinge wrote:
> +https://www.openacc.org;>OpenACC support in C, C++, and
> +Fortran continues to be maintained and improved.
> +Most of the OpenACC 2.5 specification is implemented.
> +See the
> +
Committed.
Gerald
Index: extensions.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/extensions.html,v
retrieving revision 1.62
diff -u -r1.62 extensions.html
--- extensions.html 30 Sep 2018 14:38:46 - 1.62
+++
22 matches
Mail list logo
