Hi,
while looking at the handling of basic asm statements
I noticed two minor glitches, which I want to fix now.
First there is a missing check in compare_gimple_asm in ipa-icf-gimple.c
Here we check if two asm statements are exactly identical,
there is a possibility that one is a basic asm and
Hello,
Sancov tests submitted in 231296 assume that asan is supported on all platforms.
This patch fixes that assumption.
OK for trunk?
Index: ChangeLog
===
--- ChangeLog (revision 231328)
+++ ChangeLog (working copy)
@@ -1,3 +1,8
On Sat, Dec 5, 2015 at 1:54 AM, Nathan Sidwell wrote:
> On 12/04/15 13:28, Dmitry Vyukov wrote:
>>
>> On Fri, Dec 4, 2015 at 6:39 PM, Jakub Jelinek wrote:
>>>
>>> On Fri, Dec 04, 2015 at 06:32:38PM +0100, Dmitry Vyukov wrote:
+2015-12-04 Dmitry Vyukov
+
+ * sancov.c: Ne
Hi,
while looking at the handling of basic asm statements
I noticed two minor glitches, which I want to fix now.
Secondly there is a wrong check in shorten_branches in final.c
Here we check if GET_CODE (body) == ASM_INPUT, that is
never true, because GET_CODE (body) == SEQUENCE here.
The right
The fix was posted at https://gcc.gnu.org/ml/gcc-patches/2011-08/msg00139.html
Applied on all active branches.
2015-12-06 Ludovic Brenta
PR ada/49940
* s-osinte-kfreebsd-gnu.ads (lwp_self): New imported function.
--
Eric BotcazouIndex: s-osinte-kfreebsd-gnu.ads
The fix was posted at https://gcc.gnu.org/ml/gcc-patches/2011-08/msg00594.html
Applied on all active branches.
2015-12-06 Ludovic Brenta
PR ada/49944
* s-osinte-freebsd.ads: Minor reformatting.
(Stack_Base_Available): Correct comments.
* s-osinte-kfreebsd-gnu.
Hi,
This patch fixes a some runtime issues when dealing with
the deviceptr clause in Fortran. There were some corner
cases that were not being dealt with correctly, and the
patch resolves these. Also a new set of test cases has
been added.
I've applied this patch to gomp-4_0-branch.
Jim
diff --
This just mimics what's done on FreeBSD.
Applied on all active branches.
2015-12-06 Eric Botcazou
PR ada/56274
* s-osinte-kfreebsd-gnu.ads (pthread_rwlock_t): New subtype.
(pthread_rwlockattr_t): Likewise.
--
Eric BotcazouIndex: s-osinte-kfreebsd-gnu.ads
===
Hi Uros,
> -Original Message-
> From: Stepanyan, Victoria
> Sent: Thursday, November 26, 2015 1:43 AM
> To: Uros Bizjak; gcc-patches@gcc.gnu.org
> Cc: Kumar, Venkataramanan
> Subject: RE: Add support for CLZERO ISA
>
> Thank you for the feedback, PFA fixed patch.
>
> Victoria
>
>
> -
> Bootstrapped/regtested x86_64-linux and also lto-bootstraped. Looks OK?
>
> * alias.c (alias_set_subset_of, alias_sets_conflict_p,
> objects_must_conflict_p): Short circuit for !flag_strict_aliasing
> (get_alias_set): Remove flag_strict_aliasing check.
> (new_alias_set):
Tested on x86_64-suse-linux, applied on the mainline.
2015-12-06 Eric Botcazou
PR ada/50048
* Makefile.in (ftop_srcdir): New variable.
(INCLUDES_FOR_SUBDIR): Use -iquote and $(ftop_srcdir).
2015-12-06 Eric Botcazou
PR ada/50048
* gcc-interface/Mak
Fixed all.
Now there are no new fails on spec2000
diff --git a/gcc/testsuite/gcc.target/i386/mpx/memmove.c
b/gcc/testsuite/gcc.target/i386/mpx/memmove.c
new file mode 100755
index 000..57030a3
--- /dev/null
+++ b/gcc/testsuite/gcc.target/i386/mpx/memmove.c
@@ -0,0 +1,119 @@
+/* { dg-do run } *
Hi,
Attached is a patch that fixes some runtime issues dealing
with the deviceptr clause in Fortran. There were some
corner cases that were not being dealt with correctly,
e.g., specifying the deviceptr clause and not using
the variable specified by the deviceptr clause within
the associated regi
Dear all,
currently, a coarray assignment in a program composed by a single
segment (without any sync statements) produces wrong results.
Furthermore, a coarray code
compiled with an optimization flag higher that -O0 may produce wrong
results. The patch (re)introduces a __sync_synchronize() after
Hi!
I'm not 100% sure, but I *think* that this patch
2015-11-15 Jonathan Wakely
PR libstdc++/68353
* include/bits/basic_string.h: Test value of
_GLIBCXX_USE_C99_WCHAR
not whether it is defined.
* include/ext/vstr
Hi,
I'm going to commit this patch to trunk, 5.4 and 4.9 branch if there are
no objections.
The redefinition of WCHAR_TYPE for PowerPC64 is wrong since its
beginning. My fault.
We use the definition from freebsd.h.
Thanks,
Andreas
2015-12-06 Andreas Tobler
* config/rs6000/free
On Thu, 2015-12-03 09:21:03 +, Richard Sandiford
wrote:
> All current uses of builtin_reciprocal convert 1.0/sqrt into rsqrt.
> This patch adds an rsqrt optab and associated internal function for
> that instead. We can then pick up the vector forms of rsqrt automatically,
> fixing an AArch64
I've committed the patch below to fix a build failure after
rsqrt_optab changes applied. Now rsqrtsf2 is expected to have
just 2 operands and HAVE_rsqrtsf2 should be simple enough.
Tested with build for sh4-unknown-linux-gnu and running
gcc.target/sh/sh4a-fsrra.c.
Regards,
kaz
--
2015-12-
Jan-Benedict Glaw wrote:
> shle-linux breaks with:
>
> g++ -fno-PIE -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE
> -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall
> -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute
> -Woverloaded-virtual -pedantic -Wn
Now that I can easily run the testsuite in -std=c++1z mode, I can see
various testsuite failures with that flag. This series of patches fixes
those failures.
The first fixes various issues with 'auto' deduction: We were failing to
diagnose various erroneous uses of auto, and crashing on the P
There is a minor inconsistency in the folding behavior within the C
frontend. The C frontend does not currently fold the expression "x",
where x is a const int, yet the FE does fold the expression "x + 0".
This happens because decl_constant_value is called in c_fully_fold only
while recursing ove
On Sun, Dec 6, 2015 at 11:50 PM, Patrick Palka wrote:
> There is a minor inconsistency in the folding behavior within the C
> frontend. The C frontend does not currently fold the expression "x",
> where x is a const int, yet the FE does fold the expression "x + 0".
>
> This happens because decl_c
OK.
Jason
Hi,
this is first patch to fix PR 61886 which is one of several PRs we have about
need for duplicate declarations. The cgraph code at the moment expects that
there is one declaration for every symbol. This is unfortunately not true
and in several side cases (such as fortify source, bounds checkin
Dear Alessandro, dear all,
Alessandro Fanfarillo wrote:
currently, a coarray assignment in a program composed by a single
segment (without any sync statements) produces wrong results.
Always - or only with optimization?
Furthermore, a coarray code
compiled with an optimization flag higher th
25 matches
Mail list logo