On 9/30/18 7:57 PM, H.J. Lu wrote:
> This caused:
>
> FAIL: gcc.target/i386/pr63527.c scan-assembler-not movl[ \t]%[^,]+, %ebx
> FAIL: gcc.target/i386/pr63534.c scan-assembler-not movl[ \t]%[^,]+, %ebx
> FAIL: gcc.target/i386/pr64317.c scan-assembler addl[
> \\t]+[$]_GLOBAL_OFFSET_TABLE_, %ebx
> F
On Sun, Sep 30, 2018 at 1:21 PM Peter Bergner wrote:
>
> On 9/28/18 4:34 PM, Vladimir Makarov wrote:
> > I remember I experimented with value numbering and using it in building
> > conflicts (that time it was global.c) but it did not improve the code as
> > I expected and made RA much slower.
>
>
There is no need to dynamically construct clobbers of (f)emms insn.
Also, use faster detection of vzeroall pattern.
2018-09-30 Uros Bizjak
* config/i386/mmx.md (EMMS): New int iterator.
(emms): New int attribute.
(mmx_): Macroize insn from *mmx_emms and *mmx_femms using
EMMS in
On 9/28/18 4:34 PM, Vladimir Makarov wrote:
> I remember I experimented with value numbering and using it in building
> conflicts (that time it was global.c) but it did not improve the code as
> I expected and made RA much slower.
Yes, value numbering is not cheap to compute for catching special c
Hello,
I prepared patch that give more precise control over __attribute__((warning)). Currently when you
use "warning" attribute with "-Werror" option warning become error and there is
no way to ignore this error.
With suggested changes it will be possible to use "-Werror
-Wno-error=warning-a
On 9/28/18 12:56 PM, Wilco Dijkstra wrote:
> We've seen too many instances where not keeping a well defined boundary
> between int and fp/simd leads to bad code, so not defining all possible legal
> combinations is intended. I'll check whether 32-bit w->r and w->w
> zero-extension
> could ever tri
This is a follow-up on the initial simplification I worked on this
morning, cf. https://gcc.gnu.org/ml/gcc-patches/2018-09/msg01782.html .
With this we no longer set the lang attribute to "en" via our global
style/MetaHTML pre-processing, but push lang="en" down into the
tags of all individual
Hi Paul,
First your patch has been committed with wrong entry: 65667 instead of 65677.
Second, I suspect it is responsible of the following ICE:
% gfc pr72755.f90 -fno-range-check
pr72755.f90:1485:0:
1485 | this%buffer = transfer( c(start:iend), this%buffer )
|
internal compiler error:
Now that it has got enough reviews and there's
been no comments for a week, I believe
now it's time for us to install it on trunk.
The patch is the same as previous, but rebased
on current trunk.
Could you please push it for me? If there's anything
I can do to help, just tell me.
2018-09-30 MCC
On Sun, Sep 30, 2018 at 1:53 AM Marc Glisse wrote:
>
> On Sat, 29 Sep 2018, H.J. Lu wrote:
>
> > Add pmovzx/pmovsx patterns with SI and DI operands for pmovzx/pmovsx
> > instructions which only read the low 4 or 8 bytes from the source.
>
> Hello,
>
> I am wondering a few things (these are questio
I applied the patch below. Given a number of fixes in libstdc++/doc
I've applied recently, can one of you please regenerate the HTML pages
in the next days?
Thanks,
Gerald
2018-09-30 Gerald Pfeifer
* doc/xml/manual/messages.xml: Switch link to www.oracle.com
to https.
Inde
After testing by Dominique and Juergen. Committed as revision 264725.
Thanks to Dominique and juergen for doing all the hard work!
Cheers
Paul
2018-09-30 Paul Thomas
PR fortran/87359
* trans-array.c (gfc_is_reallocatable_lhs): Correct the problem
introduced by r264358, which pre
Dear Dominique and Janne,
Putting the problem right turned out to be trivial. In the part of the
patch in gfc_conv_array_ref, what was being passed as 'decl' , in the
failing test from PR82617 was indeed an indirect reference. Applying
one dollop of indirection fixed it. The original testcase from
On Sat, Sep 29, 2018 at 9:01 PM Ian Lance Taylor wrote:
>
> "H.J. Lu" writes:
>
> > On x86-64, sys.GoarchAmd64 == 1 for -mx32. But -mx32 has 32-bit
> > pointer, not 64-bit. There is
> >
> > // _64bit = 1 on 64-bit systems, 0 on 32-bit systems
> > _64bit = 1 << (^uintptr(0) >> 63) / 2
> >
> > We
The original link was simply broken, no redirect or anything, but
I'm relatively confident this is a good replacement.
Committed.
Gerald
2018-09-30 Gerald Pfeifer
* doc/xml/manual/policy_data_structures_biblio.xml: Update
link to Microsoft Component Model Object Technologies
On Sat, 29 Sep 2018, H.J. Lu wrote:
Add pmovzx/pmovsx patterns with SI and DI operands for pmovzx/pmovsx
instructions which only read the low 4 or 8 bytes from the source.
Hello,
I am wondering a few things (these are questions, I am not asking for
changes):
Should we change the builtin an
Hi Dominique,
It's the patch for pr70752 that causes the trouble, which I had
guessed from the point in trans.c where the ICE occurs. I am onto it.
Thanks again
Paul
On Wed, 26 Sep 2018 at 16:52, Dominique d'Humières wrote:
>
> > Is se->string_length guaranteed to be of type gfc_array_index_ty
...not just for "standard" pages, those that used to be XHTML and
are now HTML 5. On the way remove traces of XHTML around that,
which were still fine, but not necessary.
Committed.
Gerald
Index: style.mhtml
===
RCS file: /cvs/gcc
18 matches
Mail list logo
