Hi Jeff:
It's updated patch,bootstrapped and run regression tested on arm-eabi,
arm-none-linux-uclibcgnueabi, x86_64-unknown-linux-gnu and nds32le-elf
without introducing regression.
Thanks for your review :)
2015-01-07 Kito Cheng
PR target/64348
* lra-constraints.c (split_re
> Xtensa is now supported by the QEMU, so probably question mark in its 'S'
> slot may be removed.
Done, thanks.
--
Eric Botcazou
On Wed, Jan 07, 2015 at 08:17:34AM +0100, Bernd Edlinger wrote:
>
> On Tue, 6 Jan 2015 16:32:35, Mike Stump wrote:
> >
> > On Jan 6, 2015, at 3:22 PM, Bernd Edlinger
> > wrote:
> >> Yes, I think too that it can't fail under these conditions.
> >
> > If you mean your version… A lot has been writt
> the attached patch removes obsolete ports (c4x, m68hc11 and ms1), toggles
> the 'p' letter and adjust accordingly (only avr, fr30, m68k, mcore, rs6000
> and sh still use define_peephole) and removes trailing spaces.
Same treatment for the 'd' letter, the ports that do not use DFA scheduler
desc
This changes makes it so that the compiler issues the same diagnostics on
invalid bit-packed array types with atomic component whatever the origin
of the Atomic aspect. For the following package:
package P is
type Arr1 is array (1 .. 16) of Boolean;
pragma Atomic_Components (Arr1);
for Arr
A new restriction No_Use_Of_Entity is implemented. The form of this is
pragma Restriction[_Warning]s (No_Use_Of_Entity => NAME), where NAME is
a fully qualified entity name. The effect is to forbid references to
this entity in the main unit, its spec, and any subunits.
The following is compiled wi
On Wed, Jan 7, 2015 at 4:03 PM, Kito Cheng wrote:
> Hi Jeff:
>
> It's updated patch,bootstrapped and run regression tested on arm-eabi,
> arm-none-linux-uclibcgnueabi, x86_64-unknown-linux-gnu and nds32le-elf
> without introducing regression.
>
> Thanks for your review :)
>
> 2015-01-07 Kito Chen
> the attached patch removes obsolete ports (c4x, m68hc11 and ms1), toggles
> the 'p' letter and adjust accordingly (only avr, fr30, m68k, mcore, rs6000
> and sh still use define_peephole) and removes trailing spaces.
This replaces 'a' with 'i' for multiple inheritance thunks and reuses 'a' for
L
This reimplements the No_Strict_Aliasing configuration pragma, which didn't
work neither for private types nor for access-to-unconstrained-array types.
The following program must compile quietly with -O2:
pragma No_Strict_Aliasing;
with Q; use Q;
package P is
type Ptr is private;
type Ar
Usually a wrapper is generated in the case of a classwide type as actual of a
generic package. In Gnatprove_Mode, and when the generic has external
axiomatizations, This wrapper is not only useless but confuses gnatprove, so
it is disabled here.
Tested on x86_64-pc-linux-gnu, committed on trunk
2
A new warning is now issued when gnatmake or gnatclean sre invoke with -P
indicationg that it is now obsolete and that the support will be removed
in the next release.
Support for project files is an advanced feature that is no longer properly
supported by gnatmake, instead the proper support has
Under certain complex circumstances, a LIMITED WITH clause can result in
an incorrect warning that the with'ed item is not referenced, when in fact
it is referenced. No simple test is available.
Tested on x86_64-pc-linux-gnu, committed on trunk
2015-01-07 Robert Dewar
* sem_warn.adb (
Use _NSGetEnviron to get environment.
Tested on x86_64-pc-linux-gnu, committed on trunk
2015-01-07 Tristan Gingold
PR ada/64349
* env.c (__gnat_environ): Adjust for darwin9/darwin10.
Index: env.c
===
--- env.c
On Tue, 2015-01-06 at 13:13 +0100, Christian Bruel wrote:
> > Please use 'gen_cmpeqsi_t (len, const0_rtx)' for comparing a value
> > against zero instead of the bit test insn.
>
> OK, also then OK to replace the other occurrences of the idiom for
> coding consistency ? (not sure if I could commit
Previously RT_Resolution was returning a hard coded dummy value.
With this change we now use the relevant system call to compute the
clock resolution.
Tested on x86_64-pc-linux-gnu, committed on trunk
2015-01-07 Doug Rupp
* s-osinte-mingw.ads (LARGE_INTEGR): New subtype.
(Quer
Some "D" files do not correspond to Ada units, and as such present no interest
for SPARK cross references. Skip these files, as printing their name may
require printing the full name with spaces, which is not handled in the code
doing I/O of SPARK cross references.
Tested on x86_64-pc-linux-gnu, c
This patch adds a warning on certain occurrences of Subprogram'Access that
could cause an access-before-elaboration error.
The following example should give a warning when compiled with the -gnatw.f
switch:
% gcc -c -gnatw.f -gnatwe elab_acc.adb
elab_acc.ads:4:31: warning: Access attribute of "F"
On Tue, Jan 6, 2015 at 7:25 PM, Uros Bizjak wrote:
>> There's suggested patch for PR ipa/64503 that was tested on x86_64 and it
>> works.
>> I would like to ask Uros to test it on an aplha machine before we install
>> the patch.
>
> Yes, this works for me on all IPA tests that were failing previo
Hi!
In 219294, I have committed a merge from trunk r219183 (2015-01-05) into
gomp-4_0-branch.
Grüße,
Thomas
pgpmnzHE1mEp2.pgp
Description: PGP signature
This patch inplements RM 7.3.2 (12/3): an invariant check must be applied to
the result of a view conversion if the type of the expression has invariants.
THe following must execute quietly:
gnatmake -q -gnata t_package_test
t_package_test
---
with Ada.Assertions; use Ada.Assertions;
with
On 01/07/2015 11:55 AM, Uros Bizjak wrote:
On Tue, Jan 6, 2015 at 7:25 PM, Uros Bizjak wrote:
There's suggested patch for PR ipa/64503 that was tested on x86_64 and it
works.
I would like to ask Uros to test it on an aplha machine before we install
the patch.
Yes, this works for me on all IP
Hello.
Following patch adds support for target and optimization nodes comparison,
which is
based on Honza's newly added infrastructure.
Apart from that, there's a small hunk that corrects formatting and removes
unnecessary
call to a comparison function.
Hope it can be applied as one patch.
T
Hi Bin:
It's 2 more line than gcc.c-torture/execute/scal-to-vec1.c since it's
need specific compilation
flag and specific target to reproduce this issue,
and it's can't reproduce by normal testing flow with
arm-*-linux-gnueabi (due to lack -fPIC flag),
so I prefer duplicate this case into gcc.targ
On 06/01/15 21:03 -0800, Tim Shen wrote:
Bootstrapped and tested. It could be also patched to 4.9 branch.
Thanks!
--
Regards,
Tim Shen
commit dfe3a26759893849020a659b14fafe8b27e90dae
Author: timshen
Date: Tue Jan 6 19:30:27 2015 -0800
PR libstdc++/64239
No blank line here in
On 26/12/14 06:46, Yury Gribov wrote:
On 12/19/2014 11:14 AM, Yury Gribov wrote:
Hi all,
Attached patch adds new check (all blocks of 8 spaces are replaced with
tabs) to contrib/check_GNU_style.sh. It also changes the script to allow
reading patches from stdin and strengthens the "Dot, space, s
Hello!
There's suggested patch for PR ipa/64503 that was tested on x86_64 and it
works.
I would like to ask Uros to test it on an aplha machine before we install
the patch.
>>>
>>> Yes, this works for me on all IPA tests that were failing previously [1].
>>>
>>> I am restarti
Hi all,
This is a backport patch for
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=213864
arm-none-eabi regression test has been done, no new issues.
Okay for branch 4.9?
gcc/ChangeLog
Fix PR target/61413
Backport from mainline.
2014-08-12 Ramana Radhakrishnan
PR target/61413
Hi all,
This is a backport patch to fix PR63424. The previous change in trunk is
here: https://gcc.gnu.org/ml/gcc-patches/2014-10/msg03306.html
and commit log is here:
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=217786
aarch64-none-elf toolchain has been tested on the model, no reg
On Wed, 7 Jan 2015 09:23:39, Jakub Jelinek wrote:
>
> But I really don't like the busy waiting. You essentially want something
> like pthread_barrier_wait that libtsan isn't aware of, right?
>
Yes.
> As tsan is only supported on x86_64-linux (and in the future could be on
> some other 64-bit li
On Wed, Jan 07, 2015 at 03:55:11PM +0100, Bernd Edlinger wrote:
> cat barrier.h
> #include
>
> static pthread_barrier_t barrier;
>
> static int (*barrier_wait)(pthread_barrier_t *);
Better
static __typeof (pthread_barrier_wait) *barrier_wait;
?
>
> __attribute__((constructor(101)))
I wouldn't
This patch by Chris Manghane fixes the Go frontend to not permit
assigning to embedded builtin types in a composite literal for an
imported struct. The builtin types are not exported names, but they
are represented as simple names rather than as hidden names (with a
leading dot). This is http://g
Previously, "test-foo.c" would be built by jit.exp as "test-foo.exe".
However, we have various test-foo.c vs test-foo.cc testcases. We don't
want them to clobber each other's executables (especially if we're going
to parallelize the jit testsuite).
Hence retain the extension, so they are built t
On Wed, Jan 07, 2015 at 12:41:57PM +, Mantas Mikaitis wrote:
> On 26/12/14 06:46, Yury Gribov wrote:
> >On 12/19/2014 11:14 AM, Yury Gribov wrote:
> >>Hi all,
> >>
> >>Attached patch adds new check (all blocks of 8 spaces are replaced with
> >>tabs) to contrib/check_GNU_style.sh. It also change
> On 07 Jan 2015, at 15:45, Joel Brobecker wrote:
>
> Hello,
>
> This patch enhances config/zlib.m4 to introduce an extra option
> --with-libz-prefix which allows us to provide the location of
> the zlib library we want to use during the build.
I prefer the gcc way to provide external library:
Would it be possible to add this patch to the gcc 4.9 branch as is? It
provides most of the basic support for reflection on ppc64 and ppc64le,
which does not work at all currently. Once I get the
libgo/go/reflect/all_test.go working I can add the patch for the fixes
and enable the testcase for
Within the jit testsuite, test-combination.c and test-threads.c rerun
other tests - the former all within one context, the latter in multiple
contexts, each on a different thread.
When reading the results of these combined tests it can be difficult to
figure out where each PASS/FAIL line actually
On Tue, Jan 6, 2015 at 7:37 AM, Lynn A. Boger
wrote:
> Add support for reflection for gccgo in gcc 4.9. This is not a backport
> because reflection support in gcc trunk is done using FFI. Bootstrap built
> and tested on ppc64, ppc64le.
Sorry, I didn't see at first that this is not a backport. T
This patch by Chris Manghane fixes the Go frontend to avoid crashes
when initializing zero-sized temporary values. This is GCC PR 61204.
Bootstrapped and ran Go testsuite on x86_64-unknown-linux-gnu.
Committed to mainline.
Ian
2015-01-07 Chris Manghane
PR go/61204
* go-gcc.cc (Gcc_backend::t
On Jan 6, 2015, at 11:17 PM, Bernd Edlinger wrote:
>
> On Tue, 6 Jan 2015 16:32:35, Mike Stump wrote:
>>
>> On Jan 6, 2015, at 3:22 PM, Bernd Edlinger wrote:
>>> Yes, I think too that it can't fail under these conditions.
>>
>> If you mean your version… A lot has been written on how to to make
I thought that since this only affects ppc64 and ppc64le, and provides
reflection support that doesnt exist in gcc 4.9 for Power (you get a
panic if you try to use reflection on ppc64, ppc64le), it would be OK.
We'll look at putting it in our own branch.
On 01/07/2015 10:06 AM, Ian Lance Taylo
On Wed, Jan 7, 2015 at 8:43 AM, Lynn A. Boger
wrote:
>
> I thought that since this only affects ppc64 and ppc64le, and provides
> reflection support that doesnt exist in gcc 4.9 for Power (you get a panic
> if you try to use reflection on ppc64, ppc64le), it would be OK.
I understand that the cod
On Jan 7, 2015, at 12:23 AM, Jakub Jelinek wrote:
> But I really don't like the busy waiting.
We’ve already determined that sched_sleep isn’t intercepted and can be used to
non-busy wait. Any reason not to use it?
> As tsan is only supported on x86_64-linux
So, I hate hardening the code to be
On Wed, Jan 07, 2015 at 08:58:04AM -0800, Mike Stump wrote:
> On Jan 7, 2015, at 12:23 AM, Jakub Jelinek wrote:
> > But I really don't like the busy waiting.
>
> We’ve already determined that sched_sleep isn’t intercepted and can be used
> to non-busy wait. Any reason not to use it?
>
> > As t
> > This patch enhances config/zlib.m4 to introduce an extra option
> > --with-libz-prefix which allows us to provide the location of
> > the zlib library we want to use during the build.
>
> I prefer the gcc way to provide external library:
>
> --with-zlib -> system zlib used
> --with-zlib=pathn
In libgo/go/reflect/makefunc.go, calls to MakeFunc, makeMethodValue and
makeValueMethod will panic if called when GOARCH is ppc64 or ppc64le.
I understand your point about what you allow into a release branch and
since it has known bugs with an existing testcase then I agree it
shouldn't be ac
On Wed, 7 Jan 2015 18:00:27, Jakub Jelinek wrote:
>
> On Wed, Jan 07, 2015 at 08:58:04AM -0800, Mike Stump wrote:
>> On Jan 7, 2015, at 12:23 AM, Jakub Jelinek wrote:
>>> But I really don't like the busy waiting.
>>
>> We’ve already determined that sched_sleep isn’t intercepted and can be used
>
On Wed, Jan 07, 2015 at 07:21:40PM +0100, Bernd Edlinger wrote:
> Ok, just for completeness, I've got the dlopen finally working:
> RTLD_NOLOAD is not working, but RTLD_LAZY or RTLD_NOW does.
No big deal I guess.
> I am however not sure if I can always use -ldl or have to use some
> target-depen
On Wed, Jan 7, 2015 at 9:26 AM, Lynn A. Boger
wrote:
>
> In libgo/go/reflect/makefunc.go, calls to MakeFunc, makeMethodValue and
> makeValueMethod will panic if called when GOARCH is ppc64 or ppc64le.
Right, I'm just saying that almost no code actually does that. I just
tried a web search and fo
This adds at least two ugly kludges to jit.exp, but it works:
in particular: the setting of tool to "g++" when loading wrapper.lib,
and the resetting of "orig_environment_saved".
I also noticed that jit-dg-test wasn't returning a list of the form:
[list $comp_output $output_file]
as dg-test assu
Committed as r219319.
gcc/jit/ChangeLog:
* jit-recording.h (gcc::jit::recording::memento_of_get_type): Fix
typo in comment.
---
gcc/jit/jit-recording.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/jit/jit-recording.h b/gcc/jit/jit-recording.h
index 17a1c
New testcase to verify that libgccjit client code can handle arithmeti
overflow.
This testcase brings jit.sum from:
# of expected passes5158
to:
# of expected passes6121
Committed to trunk as r219320.
FWIW my motivation for this testcase was due to implementing
"INT_*_OVF" op
This adds GCC_JIT_UNARY_OP_ABS to the end of enum gcc_jit_unary_op,
and so should not change ABI.
Takes jit.sum from:
# of expected passes 6121
to:
# of expected passes 6196
Committed to trunk as r219321.
gcc/jit/ChangeLog:
* docs/topics/expressions.rst (Unary Operations)
I've checked in this further patch to clean up incorrect uses of @samp
markup in invoke.texi. Per the Texinfo manual, @code should be used
instead for things that consist of entire syntactic tokens (symbol names
and language keywords, in particular, as well as larger code fragments
like expres
Hi,
this is an accepts-invalid issue about an explicit specialization
redeclared deleted. AFAICS, the problem is that start_decl sets
DECL_DELETED_FN on the fndecl too late, that is, *after* calling
grokdeclarator, whereas we want to have it set by the time the latter
calls grokfndecl, becaus
Early PING: https://gcc.gnu.org/ml/gcc-patches/2015-01/msg00090.html
Tobias Burnus wrote:
Attached is a regtested patch, which fixes the issue. Additionally,
the variable visibility (TREE_PUBLIC) is now depending on the private
attribute (copied from the module var generation) and I mark the tr
On Wed, 7 Jan 2015 19:32:16, Jakub Jelinek wrote:
>> I am however not sure if I can always use -ldl or have to use some
>> target-dependencies here.
>
> libsanitizer always puts
> -lpthread -ldl -lm
> into libsanitizer.spec, so I'd say it should be safe and you shouldn't even
> need -ldl in dg-ad
This fixes a -Wc++14-compat warning in the new libsupc++/del_ops.cc
file that defines the C++14 sized deallocation function.
Tested x86_64-linux, committed to trunk.
commit 9236910f087450f43ce80d696737e9ecd96bb1ef
Author: Jonathan Wakely
Date: Tue Jan 6 17:30:21 2015 +
* libsupc++/M
Ian Lance Taylor writes:
> On Wed, Jan 7, 2015 at 9:26 AM, Lynn A. Boger
> wrote:
>>
>> In libgo/go/reflect/makefunc.go, calls to MakeFunc, makeMethodValue and
>> makeValueMethod will panic if called when GOARCH is ppc64 or ppc64le.
>
> Right, I'm just saying that almost no code actually does th
Reject attempts to dereference a void *, otherwise we get an ICE
deep inside gimplification.
Committed to trunk as r219333.
FWIW, I ran into this as part of experiments at writing a libgccjit
backend for PyPy; see
https://bitbucket.org/pypy/pypy/branch/libgccjit-backend
In particular, the tes
On Wed, Jan 7, 2015 at 4:39 PM, Michael Hudson-Doyle
wrote:
> Ian Lance Taylor writes:
>
>> On Wed, Jan 7, 2015 at 9:26 AM, Lynn A. Boger
>> wrote:
>>>
>>> In libgo/go/reflect/makefunc.go, calls to MakeFunc, makeMethodValue and
>>> makeValueMethod will panic if called when GOARCH is ppc64 or ppc
The compiler cannot assume that the eqsi etc. patterns write a properly
extended result to a DI reg. The current way to tell it is to add an
extra pattern with an extend. This patch does that. A less cumbersome
method of specifying this would be nice -- maybe one where we say in
the SI pattern t
Ping. Any update on this patch?
https://gcc.gnu.org/ml/gcc-patches/2014-12/msg01848.html
--
Michael Collison
Linaro Toolchain Working Group
michael.colli...@linaro.org
On Wed, Jan 7, 2015 at 8:28 PM, Kito Cheng wrote:
> Hi Bin:
>
> It's 2 more line than gcc.c-torture/execute/scal-to-vec1.c since it's
> need specific compilation
> flag and specific target to reproduce this issue,
> and it's can't reproduce by normal testing flow with
> arm-*-linux-gnueabi (due to
On Wed, Jan 7, 2015 at 8:28 PM, Segher Boessenkool
wrote:
> The compiler cannot assume that the eqsi etc. patterns write a properly
> extended result to a DI reg. The current way to tell it is to add an
> extra pattern with an extend. This patch does that. A less cumbersome
> method of specifyi
The documented syntax for most GCC options that take magic keywords is
of the form @option{-ffoo=@var{magic}}, with the various literal values
for @var{magic} listed in the option description. There are a number,
though, that list the keyword choices in the syntax, but with two
different marku
PR62250 (r219171) was about some fortran tests that used atomic
operations but failing on systems where -latomic is required.
The fix was to always add -latomic. That caused test-suite
regressions for targets that don't have libatomic, but where the
required operations are built-in (no separate PR
My recent patch to remove the C++ VLA semantics that didn't make it into
C++14 missed a couple of spots. While I was looking at that I noticed
that we weren't sanitizing VLA initialization, which we ought to do;
this patch implements that. Marek, does my choice of VLA|BOUNDS make
sense to you
PING
https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01763.html
2014-10-17 Shiva Chen
Fix libatomic behavior for big endian toolchain
* cas_n.c: Fix shift amount for big endian toolchain
* config/arm/exch_n.c: Fix shift amount for big endian toolchain
* exch_n.c: Fix shift amount for big endi
68 matches
Mail list logo
