Hi,
Following patch has not been reviewed for two weeks. I think the
patch is trivial,
it doesn't affect other parts of GCC.
https://gcc.gnu.org/ml/gcc-patches/2018-05/msg01005.html
And I don't have write permission to GCC
Thanks
Zhouyi
On Mon, May 21, 2018 at 12:09 PM, Zhouyi Zhou wrot
On Sun, 3 Jun 2018, Jakub Jelinek wrote:
> Hi!
>
> We canonicalize x < type_max_val (type (x)) as x != type_max_val (type (x))
> and similarly for x > type_min_val (type (x)). Unfortunately the former
> form is what is often more beneficial for merge_ranges, if we have as in the
> testcase e.g.
On Sun, 3 Jun 2018, Jakub Jelinek wrote:
> Hi!
>
> The second argument of OMP_CRITICAL is IDENTIFIER_NODE, but we were ICEing
> on that with -Wduplicate-branches, because we didn't know how to hash it.
> operand_equal_p handles it the way it should, only pointer equal
> IDENTIFIER_NODEs are the s
On Fri, 1 Jun 2018, Joseph Myers wrote:
> On Fri, 1 Jun 2018, Michael Meissner wrote:
>
> > I'm wondering if there are other suggestions to make this patch acceptable.
> >
> > As I mentioned previously, the initialization process needs to go through
> > all
> > of the widening tables in order t
Hi,
the previous patch makes it possible to merge bit-field stores whose RHS is a
constant or a SSA name, but there is a hitch: if the SSA name is the result of
an "interesting" load, then the optimization is blocked. That's because the
GIMPLE store-merging pass not only attempts to merge stor
On Sat, 19 May 2018, Tom G. Christensen wrote:
> Latest results for 6.x
>
> Note I reformatted two of the existing entries to match the rest of the file.
Thanks, Tom! Applied now, and sorry for the delay. Business travel
has not proven helpfull.
One suggestion: Since you follow a "latest firs
On Sun, 3 Jun 2018, Jakub Jelinek wrote:
>> Push the references to our CSS from the MetaHTML style sheet into the
>> individual HTML files.
> Doesn't this affect the generated pages, like onlinedocs etc.?
In case of /onlinedocs it only affects the index pages which we
have under wwwdocs/htdocs/onl
On Sun, Jun 03, 2018 at 07:50:36PM +0200, Andreas Schwab wrote:
> * gcc.target/powerpc/altivec-7.c: Remove extra brace.
Please commit this if you haven't already. Thanks!
Segher
On Wed, 23 May 2018, Tom G. Christensen wrote:
> Latest results for 8.x
Thanks, applied.
Gerald
k
On Jun 27, 2017, Alexandre Oliva wrote:
> On Jun 26, 2017, Olivier Hainque wrote:
>> On Jun 22, 2017, at 14:12 , Alexandre Oliva wrote:
>>> Your patch takes care of the build dependencies of libcc1, which should
>>> avoid some scenarios that might lead to concurrency between staged and
>>> non-
Hello everyone,
this patch adds asynchronous I/O support. Thomas and I finally finished
a feature-complete and debugged version, so here it is. In order to use
asynchronous I/O, it is still necessary to link against libpthread,
libgomp or another library linked against any of the aforementione
* gcc.target/powerpc/altivec-7.c: Remove extra brace.
Index: gcc/testsuite/gcc.target/powerpc/altivec-7.c
===
--- gcc/testsuite/gcc.target/powerpc/altivec-7.c(revision 261129)
+++ gcc/testsuite/gcc.target/powerpc/altiv
Hi!
We canonicalize x < type_max_val (type (x)) as x != type_max_val (type (x))
and similarly for x > type_min_val (type (x)). Unfortunately the former
form is what is often more beneficial for merge_ranges, if we have as in the
testcase e.g. x >= 0 && x != __INT_MAX__, in?_p is different and we
Hi!
The second argument of OMP_CRITICAL is IDENTIFIER_NODE, but we were ICEing
on that with -Wduplicate-branches, because we didn't know how to hash it.
operand_equal_p handles it the way it should, only pointer equal
IDENTIFIER_NODEs are the same.
Bootstrapped/regtested on x86_64-linux and i686-
We were ending up with two versions of B<&l::k> internally, one with a
NOP_EXPR around the PTRMEM_CST, and the other with the conversion
folded away. Let's fold it consistently.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit c2b6fedaffe587242a7af3ffaf99298845c1243c
Author: Jason Merrill
D
This fixes an oversight in my GIMPLE store-merging patch, whereby masking out
the bits of a signed type obviously fails to turn it into an unsigned type...
And since output_merged_store will now convert to the unsigned bitfield type,
an existing conversion from a smaller type can be bypassed in p
Committed as revision 261127. The PR is closed.
The permissions of my ssh keys were changed by a system update; hence
the difficulties with updating my tree.
Paul
On 3 June 2018 at 09:29, Paul Richard Thomas
wrote:
> I was going to commit this as obvious but GNU-central seems to be
> down. I wi
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the French team of translators. The file is available at:
http://translationproject.org/latest/gcc/fr.po
(This file, 'gcc-8.1.0.fr.po', has just
I was going to commit this as obvious but GNU-central seems to be
down. I will do so when I can.
I only intend to apply it to trunk since it has been around since
2008-06-11 without any clamor to fix it :-) I don't recall why I took
it on in the first place.
Cheers
Paul
2018-06-03 Paul Thomas
Hello Rasmus,
> On 01 Jun 2018, at 14:23, Rasmus Villemoes wrote:
>
> -nostdinc apparently does not affect the directories added by the -B
> options when the xgcc wrapper is used when building an ordinary
> cross-compiler, but having -nostdinc in LIBGCC2_INCLUDES breaks a
> canadian cross build
20 matches
Mail list logo
