On 2016.12.23 at 14:25 -0700, Martin Sebor wrote:
> Bug 78703 points out that the decimal point character in floating
> directives can be longer than just one byte (in locales where the
> decimal point is a multibyte character). The decimal point can
> result in anywhere between 1 and MB_LEN_MAX b
On Fri, Dec 23, 2016 at 11:09 AM, Jakub Jelinek wrote:
> On Fri, Dec 23, 2016 at 10:09:05AM -0500, Jason Merrill wrote:
>> On Fri, Dec 23, 2016 at 3:48 AM, Jakub Jelinek wrote:
>> > Hi!
>> >
>> > C++ says that C library functions are implicitly noexcept, except for those
>> > like qsort and bsear
On Fri, Dec 23, 2016 at 04:47:22PM -0500, Michael Meissner wrote:
> I had two thinkos in my previous patches for ISA 3.0 (power9) support that
> both
> relate to word extraction and insertion.
>
> The first thinko was that I thought the index for the first byte in the 4
> bytes
> to be extracted
I had two thinkos in my previous patches for ISA 3.0 (power9) support that both
relate to word extraction and insertion.
The first thinko was that I thought the index for the first byte in the 4 bytes
to be extracted should be 0..11, when it should be 0..12. If it isn't allowed
to be 12, you cann
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-6.2.0.fr.po', has just
On December 23, 2016 6:47:37 PM GMT+01:00, Richard Sandiford
wrote:
>virtual_operand_p handled SSA names by looking at the flags of the
>underlying variable. This seems to be a relatively common source
>of cache misses, mainly because virtual_operand_p is the first thing
>tested by is_gimple_reg
Hi,
ChangeLog? Otherwise OK.
Ilya
2016-12-23 14:02 GMT+03:00 Alexander Ivchenko :
> Hi Ilya,
>
> Would that patch be OK to submit? (it is HJ's one with added testcase)
>
> diff --git a/gcc/testsuite/gcc.target/i386/mpx/memcpy-1.c
> b/gcc/testsuite/gcc.target/i386/mpx/memcpy-1.c
> new file mode 1
Georg-Johann Lay writes:
> On 22.12.2016 19:20, Richard Sandiford wrote:
>> Georg-Johann Lay writes:
>>> One test case used unsigned long for the 3rd parameter of memset, which
>>> should be size_t. This made the test crash for targets where correct
>>> parameter passing depends on correct proto
Sorry this has taken so long. In future, please feel free to ping me as
much as once a week, in email and/or IRC.
On 09/23/2016 08:41 PM, Alexandre Oliva wrote:
support aliases and trampolines in dwarf2
I know that "trampoline" is the term used in the DWARF standard, but in
GCC it typically
A big source of cache misses when compiling a recent version of
gimple-match.ii was the call to cv_cache.empty () in clear_cv_cache.
The problem was that at one early point the hash table had grown
to 8191 entries (128k on LP64 hosts). It then stayed at that size
for the rest of the compilation, e
record_reg_classes is often the hottest function when generating
unoptimised output. It seems typical for over 60% of the instructions
it handles to be moves, and of course moves tend to be the instructions
with the longest constraint strings.
Maybe we should avoid using move constraints to set c
virtual_operand_p handled SSA names by looking at the flags of the
underlying variable. This seems to be a relatively common source
of cache misses, mainly because virtual_operand_p is the first thing
tested by is_gimple_reg.
This patch caches the information in the SSA name itself. Several
flag
On Fri, Dec 23, 2016 at 05:54:01PM +0100, Georg-Johann Lay wrote:
> >The purpose of the combine change is to write widening extracts in a
> >more general form, so that backends for processors that can do such
> >more general things do not have to write hundreds (literally) extra
> >patterns for all
Segher Boessenkool schrieb:
On Thu, Dec 22, 2016 at 04:18:34PM +0100, Georg-Johann Lay wrote:
If you don't have instruction scheduling subregs of mem are allowed (and
are counted as registers). Combine asks recog, and it think this is
fine.
Why does reload use r31 here? Why does it think th
On Fri, Dec 23, 2016 at 10:09:05AM -0500, Jason Merrill wrote:
> On Fri, Dec 23, 2016 at 3:48 AM, Jakub Jelinek wrote:
> > Hi!
> >
> > C++ says that C library functions are implicitly noexcept, except for those
> > like qsort and bsearch where exceptions can be thrown from the callbacks.
> >
> > W
On Fri, Dec 16, 2016 at 10:45 AM, Jonathan Wakely wrote:
> On 15/12/16 21:41 -0300, Felipe Magno de Almeida wrote:
>>
>> Good point. Do you want me to update the patch with __men or go your way
>> with the wrapper?
Hello Jonathan,
> I think my wrapper's too ugly :-)
:)
> So please follow the s
On Fri, Dec 23, 2016 at 3:48 AM, Jakub Jelinek wrote:
> Hi!
>
> C++ says that C library functions are implicitly noexcept, except for those
> like qsort and bsearch where exceptions can be thrown from the callbacks.
>
> We handle this through cfns.gperf, but that contains only list of C89
> functi
In order to handle large character lengths on (L)LP64 targets, switch
the GFortran character length from an int to a size_t.
This is an ABI change, as procedures with character arguments take
hidden arguments with the character length.
I also changed the _size member in vtables from int to size_t
Hi Ilya,
Would that patch be OK to submit? (it is HJ's one with added testcase)
diff --git a/gcc/testsuite/gcc.target/i386/mpx/memcpy-1.c
b/gcc/testsuite/gcc.target/i386/mpx/memcpy-1.c
new file mode 100644
index 000..1691348
--- /dev/null
+++ b/gcc/testsuite/gcc.target/i386/mpx/memcpy-1.c
@@
On 22.12.2016 19:20, Richard Sandiford wrote:
Georg-Johann Lay writes:
One test case used unsigned long for the 3rd parameter of memset, which
should be size_t. This made the test crash for targets where correct
parameter passing depends on correct prototypes.
Fixed and committed as obvious.
Hi Janus, hi all,
thanks for the review. Committed as r243909.
Regards,
Andre
On Thu, 22 Dec 2016 23:26:19 +0100
Janus Weil wrote:
> 2016-12-20 17:07 GMT+01:00 Andre Vehreschild :
> > Hi Janus,
> >
> >> 1) After adding that code block in gfc_trans_assignment_1, it seems
> >> like the
> From: Catherine Moore
>
> >
> > gcc/testsuite/ChangeLog:
> >
> > * gcc.target/mips/oddspreg-2.c (dg-options): Remove dg-skip-if
> > for
> > -fno-fat-lto-objects and add the -ffat-lto-objects option, along
> > with
> > an explanation for its purpose.
> > * gcc.target/mips/oddspreg
On Wed, Dec 21, 2016 at 3:14 PM, Andre Vehreschild wrote:
>> Now when I think about this some more, I have a vague recollection
>> that a long time ago it used to be something like that. The problem
>> is that MIN_EXPR will of course be
>> NON-CONSTANT, so the memcpy call can't be inlined. Hence
Hi!
C++ says that C library functions are implicitly noexcept, except for those
like qsort and bsearch where exceptions can be thrown from the callbacks.
We handle this through cfns.gperf, but that contains only list of C89
functions, while C++11 and C++14 refer to C99 and C++17 refers to C11.
I
24 matches
Mail list logo
