Hi Alexandre,
On 6 January 2017 at 04:27, Alexandre Oliva wrote:
> On Jan 5, 2017, Jeff Law wrote:
>
>> On 01/05/2017 05:15 AM, Richard Biener wrote:
>>> Reasonable -- I'll leave it for others to comment on that "standard
>>> practice" part (it'll be the first case of using this IIRC).
>
>> It'
2017-01-02 19:22 GMT+04:00 Georg-Johann Lay :
> On 02.01.2017 15:54, Dominik Vogt wrote:
>>
>> On Mon, Jan 02, 2017 at 03:47:43PM +0100, Georg-Johann Lay wrote:
>>>
>>> This fixes PR78883 which is a problem in reload revealed by a
>>> change to combine.c. The fix is as proposed by Segher: implemen
On Jan 06 2017, Alexandre Oliva wrote:
> On Jan 5, 2017, Andreas Schwab wrote:
>
>> On Jan 05 2017, Alexandre Oliva wrote:
>>> On Jan 5, 2017, Andreas Schwab wrote:
>>>
On Jan 05 2017, Alexandre Oliva wrote:
> - sprintf (xname, "", ((unsigned)((uintptr_t)(t) & 0x)));
On Thu, Jan 05, 2017 at 05:58:01PM +, Joseph Myers wrote:
> On Thu, 5 Jan 2017, Michael Eager wrote:
>
> > On multiple occasions, I have asked Xilinx to submit patches such
> > as this one directly to the GCC/Binutils projects (assuming that
> > they have a current FSF Copyright As
On Fri, Jan 06, 2017 at 12:49:54AM -0200, Alexandre Oliva wrote:
> On Jan 5, 2017, Jakub Jelinek wrote:
>
> > You've just changed the hash function and my mail was about the fact that
> > it is not enough.
>
> Sorry, it wasn't clear 'enough for what'. It's enough to fix the
> bug/symptom I had
On 05/01/17 18:32, Wilco Dijkstra wrote:
With -fpu=neon DI mode shifts are expanded after reload. DI mode registers can
either fully or partially overlap on both ARM and Thumb-2. However the shift
expansion code can only deal with the full overlap case, and generates incorrect
code for partial
On January 6, 2017 3:49:54 AM GMT+01:00, Alexandre Oliva
wrote:
>On Jan 5, 2017, Jakub Jelinek wrote:
>
>> You've just changed the hash function and my mail was about the fact
>that
>> it is not enough.
>
>Sorry, it wasn't clear 'enough for what'. It's enough to fix the
>bug/symptom I had obse
On 01/06/2017 10:46 AM, Jakub Jelinek wrote:
> On Fri, Jan 06, 2017 at 12:49:54AM -0200, Alexandre Oliva wrote:
>> On Jan 5, 2017, Jakub Jelinek wrote:
>>
>>> You've just changed the hash function and my mail was about the fact that
>>> it is not enough.
>>
>> Sorry, it wasn't clear 'enough for w
On 01/06/2017 11:07 AM, Richard Biener wrote:
> On January 6, 2017 3:49:54 AM GMT+01:00, Alexandre Oliva
> wrote:
>> On Jan 5, 2017, Jakub Jelinek wrote:
>>
>>> You've just changed the hash function and my mail was about the fact
>> that
>>> it is not enough.
>>
>> Sorry, it wasn't clear 'enoug
On January 6, 2017 2:57:49 AM GMT+01:00, David Malcolm
wrote:
>The GIMPLE frontend's pass-skipping logic in execute_one_pass is
>somewhat
>awkward. This patch splits it out into two subroutines to simplify
>things.
>
>No functional change intended (and this may make it easier to
>update the logi
On Fri, Jan 06, 2017 at 09:34:46AM +0100, Christophe Lyon wrote:
> I makes my aarch64*linux* and arm*linux* builds for fail, because:
> gcc/fortran/simplify.c:613: error: #pragma GCC diagnostic not allowed
> inside functions
> gcc/fortran/simplify.c:620: error: #pragma GCC diagnostic not allowed
>
This patch modifies the expansion of attribute 'Read to ensure that relevant
checks are properly installed on the return value obtained by calling the
related Read routine. This is done by means of a type conversion to the
target type.
-- Source --
-- types.ads
with Ad
This patch fixes a bug where the compiler would add an implicit pragma
Elaborate_All(P) to the body of P itself, causing gnatbind to find a
spurious elaboration cycle.
The following test must build quietly.
gnatmake -q -f main.adb
with Ada.Finalization;
package Ctrl is
type T (Object : acces
Make Linux specific option SO_BUSY_POLL accessable as Busy_Polling
option. Also offer a generic API to set options that were not available
at compiler build time.
Tested on x86_64-pc-linux-gnu, committed on trunk
2017-01-06 Thomas Quinot
* s-oscons-tmplt.c, g-socket.adb, g-socket.ads,
This patch updates the funalization mechanism to correctly recognize a
redefined unary operator which returns an interface class-wide type. Such
objects require finalization actions.
-- Source --
-- types.ads
with Ada.Finalization; use Ada.Finalization;
package Types
This patch implements the semantics of aspect/pragma Max_Queue_Length
which restricts the entry queue length for protected entries by allowing
the aspect and pragma Max_Queue_Length to appear directly after protected
entries followed by a single argument -- a positive integer.
To achieve the runti
On 09/12/16 16:31, Bernd Schmidt wrote:
> On 12/09/2016 05:16 PM, Andre Vieira (lists) wrote:
>
>> Regardless, 'reload_cse_simplify' would never perform the opposite
>> transformation. It checks whether it can replace anything within the
>> first argument INSN, with the second argument TESTREG. A
This patch creates a new attribute Finalization_Size for all objects. Its
result is an integer which represents the internal header size (including
padding) required by the object's type to store the additional data used
during finalization.
-- Source --
-- fail.ads
wi
This patch fixes a spurious error on a case statement whose expression is a
type conversion of a variable whose initial value is known, and whose type
has a static predicate.
Executing:
gnatmake -q static_predicate_example
static_predicate_example
gnatmake -q -f -gnata static_predicate_e
On 11/11/16 18:22, Jiong Wang wrote:
This patch add command line support for ARMv8.3-A through new architecture:
-march=armv8.3-a
ARMv8.3-A implies all default features of ARMv8.2-A and meanwhile it includes
the new pointer authentication extension.
gcc/
2016-11-08 Jiong Wang
*
On 6 January 2017 at 11:21, Jakub Jelinek wrote:
> On Fri, Jan 06, 2017 at 09:34:46AM +0100, Christophe Lyon wrote:
>> I makes my aarch64*linux* and arm*linux* builds for fail, because:
>> gcc/fortran/simplify.c:613: error: #pragma GCC diagnostic not allowed
>> inside functions
>> gcc/fortran/simp
On January 6, 2017 11:21:44 AM GMT+01:00, Jakub Jelinek
wrote:
>On Fri, Jan 06, 2017 at 09:34:46AM +0100, Christophe Lyon wrote:
>> I makes my aarch64*linux* and arm*linux* builds for fail, because:
>> gcc/fortran/simplify.c:613: error: #pragma GCC diagnostic not allowed
>> inside functions
>> gc
On 11/11/16 18:22, Jiong Wang wrote:
As described in the cover letter, this patch implements return address signing
for AArch64, it's controlled by the new option:
-msign-return-address=[none | non-leaf | all]
"none" means don't do return address signing at all on any function. "non-leaf"
m
On 11/11/16 18:22, Jiong Wang wrote:
This patch generate DWARF description for pointer authentication. DWARF value
expression is used to describe the authentication action.
Please see the cover letter and AArch64 DWARF specification for the semantics
of AArch64 DWARF operations.
When authentic
On 11/11/16 18:22, Jiong Wang wrote:
This patch add AArch64 specific runtime EH unwinding support for
DW_OP_AARCH64_pauth, DW_OP_AARCH64_paciasp and DW_OP_AARCH64_paciasp_deref.
The semantics of them are described at the specification in patch [1/9].
The support includes:
* Parsing these DWA
On 11/11/16 18:22, Jiong Wang wrote:
We need customized EH unwinder support for AArch64 DWARF operations introduced
earlier in this patchset, these changes mostly need to be done in the generic
file unwind-dw2.c.
There are two ways of introducing these AArch64 support:
* Introducing a few tar
On 11/11/16 18:22, Jiong Wang wrote:
This patch implements a few ARMv8.3-A new builtins for pointer sign and
authentication instructions.
Currently, these builtins are supposed to be used by libgcc EH unwinder
only. They are not public interface to external user.
OK to install?
gcc/
2016-11-1
Hi all,
In this wrong-code issue the RTL tries to load a const_vector:
(const_vector:V8QI [
(const_int 1 [0x1])
(const_int 0 [0])
(const_int 1 [0x1])
(const_int 0 [0])
(const_int 1 [0x1])
(const_int 0 [0])
(const_int 1 [0x1])
(const_
This patch implements a new GNAT-specific pragma Rename_Pragma, which is
helpful when porting code from other compilers that have similar pragmas but
with different names.
pragma Rename_Pragma
(New_Name => Inline_Only,
Renamed => Inline_Always);
causes GNAT to treat "pragma Inli
This Flush routine is equivalent to the one found in the Text_IO
package for example.
The Flush procedure synchronizes the external file with the internal
file (by flushing any internal buffers) without closing the file.
Tested on x86_64-pc-linux-gnu, committed on trunk
2017-01-06 Pascal Obry
This patch provides a GNAT specific aspect and pragma Secondary_Stack_Size
that enables users to specify the size of the secondary stack for each
task type. On targets that use dynamic secondary stack size allocation,
this pragma defines the initial size of the secondary stack. On targets
using fix
On 5 January 2017 at 05:00, Gerald Pfeifer wrote:
> In case you are wondering, Siddhesh, Richard was referring
> to https://gcc.gnu.org/gcc-7/changes.html and at
> https://gcc.gnu.org/about.html you'll find some documentation
> on how to go about updating that.
I did post a patch and you reviewe
Hi,
This patch documents the newly added flag in gcc 7 for the upcoming
Qualcomm Falkor processor core.
Siddhesh
Index: htdocs/gcc-7/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-7/changes.html,v
retrieving revision 1.33
di
This avoids a potential redefinition warning if users define both
_GLIBCXX_DEBUG and _GLIBCXX_ASSERTIONS.
* include/bits/c++config (_GLIBCXX_ASSERTIONS): Avoid redefinition.
Tested powerpc64le-linux, committed to trunk.
commit e6b4586112080ac1912d336451207cba963a2c48
Author: Jonathan Wa
This solves a problem when using libstdc++ with Clang, due to Clang
more eagerly instantiating constexpr function templates during
argument deduction. G++ has some shortcuts to avoid this problem, but
Clang doesn't, and it's not clear that it's strictly speaking a bug in
Clang or if it's following
Hello.
This enables doable LTO bootstrap w/o -disable-werror. First change is mentioned
in the PR, second is adding -fno-lto to libdecnumber. Honza told me that proper
fix would take more effort as it's an old library. Last needed hunk handles
-Wmaybe-uninitialized,
as described in https://gcc.gn
Hi David,
> The various parts of patch 8 appear to now have been approved, so
> I've committed it (along with "Add ASSERT_RTX_PTR_EQ", which it
> requires and is required by) to trunk as r244110, having rebased,
> and bootstrapped & regrtested on x86_64-pc-linux-gnu, and tested
> stage 1's selftes
On Fri, Jan 06, 2017 at 01:41:15PM +0100, Martin Liška wrote:
> Hello.
>
> This enables doable LTO bootstrap w/o -disable-werror. First change is
> mentioned
> in the PR, second is adding -fno-lto to libdecnumber. Honza told me that
> proper
> fix would take more effort as it's an old library. L
On 07/12/16 11:46 -0600, Aditya Kumar wrote:
Here is an improved version of basic_string::find. The idea is to
split the string find in two parts:
1. search for the first match by using traits_type::find (this gets converted
to memchr for x86)
2. see if there is a match (this gets converted to m
In debugging an lto problem, I fixed up some comments and formatting I
stumbled across.
Committed as obvious.
nathan
--
Nathan Sidwell
2017-01-06 Nathan Sidwell
gcc/
* ipa-visibility.c (function_and_variable_visibility): Reformat
comments and long lines. Remove extrneous if.
* symtab.c
This patch helped me diagnose the LTO bug I'm working on. It adds
dumping of alias promotion, just after the symbol they alias.
committed as obvious.
nathan
--
Nathan Sidwell
2017-01-06 Nathan Sidwell
* lto-partition.c (promote_symbol): Write to dump file sooner,
include alias promoting
On Thu, Jan 5, 2017 at 1:20 AM, Rainer Orth
wrote:
> As could have been expected, the static libgo.a causes the same problem
> with hardware capabilities on Solaris/x86 as was solved for libgo.so
> with
>
> https://gcc.gnu.org/ml/gcc-patches/2016-12/msg00726.html
>
> Instead of trying to
On 05/01/17 10:27, Kyrill Tkachov wrote:
>
> On 05/12/16 15:05, Andre Vieira (lists) wrote:
>> On 01/12/16 17:25, Andre Vieira (lists) wrote:
>>> On 09/11/16 10:11, Andre Vieira (lists) wrote:
Hi,
This patch refactors the implementation of the ARM ACLE CRC builtins to
use the b
On 05/01/17 10:44, Kyrill Tkachov wrote:
> Hi Andre,
>
> On 09/11/16 10:11, Andre Vieira (lists) wrote:
>> Hi,
>>
>> This patch implements support for the ARM ACLE Coprocessor CDP
>> intrinsics. See below a table mapping the intrinsics to their respective
>> instructions:
>>
>> +--
On 05/01/17 11:02, Kyrill Tkachov wrote:
> Hi Andre,
>
> On 09/11/16 10:12, Andre Vieira (lists) wrote:
>> Hi,
>>
>> This patch implements support for the ARM ACLE Coprocessor LDC and STC
>> intrinsics. See below a table mapping the intrinsics to their respective
>> instructions:
>>
>> +--
On 05/01/17 11:08, Kyrill Tkachov wrote:
>
> On 09/11/16 10:12, Andre Vieira (lists) wrote:
>> Hi,
>>
>> This patch implements support for the ARM ACLE Coprocessor MCR and MRC
>> intrinsics. See below a table mapping the intrinsics to their respective
>> instructions:
>>
>> +--
Hi Ian,
> On Thu, Jan 5, 2017 at 1:20 AM, Rainer Orth
> wrote:
>> As could have been expected, the static libgo.a causes the same problem
>> with hardware capabilities on Solaris/x86 as was solved for libgo.so
>> with
>>
>> https://gcc.gnu.org/ml/gcc-patches/2016-12/msg00726.html
>>
>> I
Yes, we do.
Sorry for the mistake, it happened because I first wrote this for
libcxx (https://reviews.llvm.org/D27068) and while porting that line
got missed.
Thanks,
-Aditya
diff --git a/libstdc++-v3/include/bits/basic_string.tcc
b/libstdc++-v3/include/bits/basic_string.tcc
index df1e8dd..7942e
On 05/01/17 11:11, Kyrill Tkachov wrote:
> Hi Andre,
>
> On 09/11/16 10:12, Andre Vieira (lists) wrote:
>> Hi,
>>
>> This patch implements support for the ARM ACLE Coprocessor MCR and MRC
>> intrinsics. See below a table mapping the intrinsics to their respective
>> instructions:
>>
>> +--
On Fri, Jan 06, 2017 at 08:42:15AM -0600, Aditya Kumar wrote:
> Yes, we do.
> Sorry for the mistake, it happened because I first wrote this for
> libcxx (https://reviews.llvm.org/D27068) and while porting that line
> got missed.
Shouldn't find at least in the case where it is narrow char string
ju
On 06/01/17 16:09 +0100, Jakub Jelinek wrote:
On Fri, Jan 06, 2017 at 08:42:15AM -0600, Aditya Kumar wrote:
Yes, we do.
Sorry for the mistake, it happened because I first wrote this for
libcxx (https://reviews.llvm.org/D27068) and while porting that line
got missed.
Shouldn't find at least in
On 06/01/17 14:17, Andre Vieira (lists) wrote:
On 05/01/17 10:44, Kyrill Tkachov wrote:
Hi Andre,
On 09/11/16 10:11, Andre Vieira (lists) wrote:
Hi,
This patch implements support for the ARM ACLE Coprocessor CDP
intrinsics. See below a table mapping the intrinsics to their respective
instruc
On 06/01/17 14:58, Andre Vieira (lists) wrote:
On 05/01/17 11:11, Kyrill Tkachov wrote:
Hi Andre,
On 09/11/16 10:12, Andre Vieira (lists) wrote:
Hi,
This patch implements support for the ARM ACLE Coprocessor MCR and MRC
intrinsics. See below a table mapping the intrinsics to their respective
On 06/01/17 14:18, Andre Vieira (lists) wrote:
On 05/01/17 11:08, Kyrill Tkachov wrote:
On 09/11/16 10:12, Andre Vieira (lists) wrote:
Hi,
This patch implements support for the ARM ACLE Coprocessor MCR and MRC
intrinsics. See below a table mapping the intrinsics to their respective
instructio
On 06/01/17 14:18, Andre Vieira (lists) wrote:
On 05/01/17 11:02, Kyrill Tkachov wrote:
Hi Andre,
On 09/11/16 10:12, Andre Vieira (lists) wrote:
Hi,
This patch implements support for the ARM ACLE Coprocessor LDC and STC
intrinsics. See below a table mapping the intrinsics to their respective
Hi Jeff,
On 5 January 2017 at 09:34, Richard Biener wrote:
> On Wed, Jan 4, 2017 at 8:24 PM, Jeff Law wrote:
>> On 01/04/2017 11:55 AM, Jeff Law wrote:
>>>
>>> On 12/09/2016 01:28 AM, Richard Biener wrote:
On Wed, Dec 7, 2016 at 12:18 AM, Jeff Law wrote:
>
>
>
> So I
PING^1
On 12/22/2016 02:38 PM, Martin Liška wrote:
> Hello.
>
> As I previously agreed with Jakub, I prepared patch which adds
> no_sanitize function attribute (same what clang support).
>
> That encompasses following changes:
> 1) all no_sanitize_* function attributes are parsed and stored to
On 23/12/16 01:20 +, Jonathan Wakely wrote:
On 22/12/16 19:06 -0600, Barrett Adair wrote:
On Tue, Dec 6, 2016 at 1:24 PM, Tim Shen wrote:
On Tue, Dec 6, 2016 at 4:35 AM, Jonathan Wakely wrote:
I've rebased Barrett's patch against the latest variant code
(attached).
Tim, do we want to ma
On Fri, Jan 06, 2017 at 03:16:12PM +, Jonathan Wakely wrote:
> On 06/01/17 16:09 +0100, Jakub Jelinek wrote:
> > On Fri, Jan 06, 2017 at 08:42:15AM -0600, Aditya Kumar wrote:
> > > Yes, we do.
> > > Sorry for the mistake, it happened because I first wrote this for
> > > libcxx (https://reviews.
On 06/01/17 16:26 +0100, Jakub Jelinek wrote:
On Fri, Jan 06, 2017 at 03:16:12PM +, Jonathan Wakely wrote:
On 06/01/17 16:09 +0100, Jakub Jelinek wrote:
> On Fri, Jan 06, 2017 at 08:42:15AM -0600, Aditya Kumar wrote:
> > Yes, we do.
> > Sorry for the mistake, it happened because I first wrot
On Fri, Jan 06, 2017 at 03:34:22PM +, Jonathan Wakely wrote:
> > The description of Two-Way algorithm is in
> > http://www-igm.univ-mlv.fr/~lecroq/string/node26.html#SECTION00260
> > Boyer-Moore in
> > http://en.wikipedia.org/wiki/Boyer-Moore_string_search_algorithm
>
> And in std::boyer_moore
On 01/06/2017 04:34 AM, Christophe Lyon wrote:
On 6 January 2017 at 11:21, Jakub Jelinek wrote:
On Fri, Jan 06, 2017 at 09:34:46AM +0100, Christophe Lyon wrote:
I makes my aarch64*linux* and arm*linux* builds for fail, because:
gcc/fortran/simplify.c:613: error: #pragma GCC diagnostic not allo
On 01/06/2017 04:39 AM, Richard Biener wrote:
On January 6, 2017 11:21:44 AM GMT+01:00, Jakub Jelinek
wrote:
On Fri, Jan 06, 2017 at 09:34:46AM +0100, Christophe Lyon wrote:
I makes my aarch64*linux* and arm*linux* builds for fail, because:
gcc/fortran/simplify.c:613: error: #pragma GCC diagn
On 01/06/2017 03:53 AM, Andre Vieira (lists) wrote:
On 09/12/16 16:31, Bernd Schmidt wrote:
On 12/09/2016 05:16 PM, Andre Vieira (lists) wrote:
Regardless, 'reload_cse_simplify' would never perform the opposite
transformation. It checks whether it can replace anything within the
first argumen
On Fri, Jan 6, 2017 at 6:35 AM, Rainer Orth
wrote:
> Hi Ian,
>
>> On Thu, Jan 5, 2017 at 1:20 AM, Rainer Orth
>> wrote:
>>> As could have been expected, the static libgo.a causes the same problem
>>> with hardware capabilities on Solaris/x86 as was solved for libgo.so
>>> with
>>>
>>> h
This fixes / works-around the wrong-code PR57583 on M68K, caused by
overflowing the 16-bit jump table offsets the backend uses.
Ideally the backend should define CASE_VECTOR_SHORTEN_MODE, but that
AFAIK needs insn length attributes, which the backend only has for CF
but not for classic M68K.
Inst
Hi,
this is next patch to tweak call predictors. It fixes bug in the direction of
predictor (like normal calls, polymorphic calls are usually not taken when
there is if guariding them) and feeds in correct data from Martin's table.
Bootstrapped/regtested x86_64-linux, comitted.
I will fix the ind
On 6 January 2017 at 12:39, Richard Biener wrote:
> On January 6, 2017 11:21:44 AM GMT+01:00, Jakub Jelinek
> wrote:
>>On Fri, Jan 06, 2017 at 09:34:46AM +0100, Christophe Lyon wrote:
>>> I makes my aarch64*linux* and arm*linux* builds for fail, because:
>>> gcc/fortran/simplify.c:613: error: #p
Hi,
On 6 January 2017 at 13:54, Jakub Jelinek wrote:
> On Fri, Jan 06, 2017 at 01:41:15PM +0100, Martin Liška wrote:
>> Hello.
>>
>> This enables doable LTO bootstrap w/o -disable-werror. First change is
>> mentioned
>> in the PR, second is adding -fno-lto to libdecnumber. Honza told me that
>
On Fri, Jan 06, 2017 at 05:11:51PM +0100, Jan Hubicka wrote:
> Index: ChangeLog
> ===
> --- ChangeLog (revision 244166)
> +++ ChangeLog (working copy)
> @@ -1,3 +1,10 @@
> +2017-01-01 Jan Hubicka
> +
> + PR middle-end/77484
> +
> On Fri, Jan 06, 2017 at 05:11:51PM +0100, Jan Hubicka wrote:
> > Index: ChangeLog
> > ===
> > --- ChangeLog (revision 244166)
> > +++ ChangeLog (working copy)
> > @@ -1,3 +1,10 @@
> > +2017-01-01 Jan Hubicka
> > +
> >
On 01/05/2017 08:52 PM, Martin Sebor wrote:
So Richi asked for removal of the VR_ANTI_RANGE handling, which would
imply removal of operand_signed_p.
What are the implications if we do that?
I just got back to this yesterday. The implications of the removal
of the anti-range handling are a num
On Thu, Jan 05, 2017 at 03:20:26PM -0500, David Malcolm wrote:
> + /* Handle "reuse_rtx". */
> + if (strcmp (code_name, "reuse_rtx") == 0)
> +{
> + read_name (&name);
> + long idx = atoi (name.string);
> + /* Look it up by ID. */
> + gcc_assert (idx < m_reuse_rtx_by_id.l
On Fri, Jan 06, 2017 at 05:12:54PM +0100, Christophe Lyon wrote:
> This makes all my builds fail.
> (The *linux* ones are broken after Alexandre's pragma, and
> this commit breaks the remaining bare-metal configurations).
> make[2]: Entering directory
> `/tmp/3119026_6.tmpdir/aci-gcc-fsf/builds/gcc
On 01/06/2017 01:34 AM, Edgar E. Iglesias wrote:
On Thu, Jan 05, 2017 at 05:58:01PM +, Joseph Myers wrote:
On Thu, 5 Jan 2017, Michael Eager wrote:
On multiple occasions, I have asked Xilinx to submit patches such
as this one directly to the GCC/Binutils projects (assuming that
On Fri, 2017-01-06 at 17:25 +0100, Jakub Jelinek wrote:
> On Thu, Jan 05, 2017 at 03:20:26PM -0500, David Malcolm wrote:
> > + /* Handle "reuse_rtx". */
> > + if (strcmp (code_name, "reuse_rtx") == 0)
> > +{
> > + read_name (&name);
> > + long idx = atoi (name.string);
> > + /
On 01/05/2017 08:52 PM, Martin Sebor wrote:
So Richi asked for removal of the VR_ANTI_RANGE handling, which would
imply removal of operand_signed_p.
What are the implications if we do that?
I just got back to this yesterday. The implications of the removal
of the anti-range handling are a num
On 05/01/17 12:09, Kyrill Tkachov wrote:
On 05/01/17 12:01, Richard Biener wrote:
On Wed, Jan 4, 2017 at 4:07 PM, Kyrill Tkachov
wrote:
On 04/01/17 14:19, Richard Biener wrote:
On Wed, Dec 21, 2016 at 10:40 AM, Kyrill Tkachov
wrote:
On 20/12/16 17:30, Richard Biener wrote:
On December 20
On Fri, Jan 06, 2017 at 05:33:03PM +0100, Jakub Jelinek wrote:
> On Fri, Jan 06, 2017 at 05:12:54PM +0100, Christophe Lyon wrote:
> > This makes all my builds fail.
> > (The *linux* ones are broken after Alexandre's pragma, and
> > this commit breaks the remaining bare-metal configurations).
> > ma
Ping!
On Wed, 28 Dec 2016 20:31:16 +0100
Andre Vehreschild wrote:
> Hi all,
>
> attached patch fixes and implements pointer components in derived typed
> coarrays. The testcase in the description also has a class coarray, which is
> still not implemented but tracked by pr77961. Therefore only t
On 6 January 2017 at 17:46, Jakub Jelinek wrote:
> On Fri, Jan 06, 2017 at 05:33:03PM +0100, Jakub Jelinek wrote:
>> On Fri, Jan 06, 2017 at 05:12:54PM +0100, Christophe Lyon wrote:
>> > This makes all my builds fail.
>> > (The *linux* ones are broken after Alexandre's pragma, and
>> > this commit
On 04/01/17 15:42 +, Jonathan Wakely wrote:
FreeBSD 11 adds __cxa_thread_atexit to libc, so we should use that
instead of defining our own inferior version. This also avoids
multiple definitions of the symbol.
PR libstdc++/78968
* config.h.in: Regenerate.
* configure:
Another approach would be to walk the SSA_NAME list and generate a
bitmap of all the names which have a signed type or which were defined
by a conversion to an unsigned type from a signed type.
At that point what's left is just the PHIs. So we'd walk the dominator
tree in RPO order to proc
On 01/06/2017 09:08 AM, Mikael Pettersson wrote:
This fixes / works-around the wrong-code PR57583 on M68K, caused by
overflowing the 16-bit jump table offsets the backend uses.
Ideally the backend should define CASE_VECTOR_SHORTEN_MODE, but that
AFAIK needs insn length attributes, which the back
On 01/06/2017 09:43 AM, David Malcolm wrote:
On Fri, 2017-01-06 at 17:25 +0100, Jakub Jelinek wrote:
On Thu, Jan 05, 2017 at 03:20:26PM -0500, David Malcolm wrote:
+ /* Handle "reuse_rtx". */
+ if (strcmp (code_name, "reuse_rtx") == 0)
+{
+ read_name (&name);
+ long idx = atoi
On Fri, 2017-01-06 at 10:25 -0700, Jeff Law wrote:
> On 01/06/2017 09:43 AM, David Malcolm wrote:
> > On Fri, 2017-01-06 at 17:25 +0100, Jakub Jelinek wrote:
> > > On Thu, Jan 05, 2017 at 03:20:26PM -0500, David Malcolm wrote:
> > > > + /* Handle "reuse_rtx". */
> > > > + if (strcmp (code_name,
On 12/23/2016 10:50 AM, Richard Sandiford wrote:
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.
Ma
This performance test has been broken since we modified VERIFY to not
depend on assert. This fixes it.
* testsuite/util/performance/priority_queue/mem_usage/pop_test.hpp:
Include header.
Tested x86_64-linux. Committed to trunk.
commit d89e1655fd1475a16a4a2b338f679451206d792c
Au
On January 6, 2017 5:45:46 PM GMT+01:00, Kyrill Tkachov
wrote:
>
>On 05/01/17 12:09, Kyrill Tkachov wrote:
>>
>> On 05/01/17 12:01, Richard Biener wrote:
>>> On Wed, Jan 4, 2017 at 4:07 PM, Kyrill Tkachov
>>> wrote:
On 04/01/17 14:19, Richard Biener wrote:
> On Wed, Dec 21, 2016 at 10:4
On 01/06/2017 01:48 AM, Segher Boessenkool wrote:
On Thu, Jan 05, 2017 at 01:21:40PM -0600, Bill Seurer wrote:
(backport from trunk to gcc 6)
This patch adds the -fasynchronous-unwind-tables option to compilations when
the -fsanitize=address option is seen but not if any
-fasynchronous-unwind-t
Hi,
On Wed, Dec 14, 2016 at 01:12:11PM +0100, Richard Biener wrote:
> On Wed, Dec 14, 2016 at 11:15 AM, Martin Jambor wrote:
> > ...
> > +/* Emulate effects of unary OPERATION and/or conversion from SRC_TYPE to
> > + DST_TYPE on value range in SRC_VR and store it to DST_VR. Return true
> >
Jeff,
Thanks for the review. Committed as 244177 with requested changes.
2017-01-06 Aaron Sawdey
* gcc.dg/memcmp-1.c: New.
* gcc.dg/strncmp-1.c: New.
Aaron
On 12/23/2016 02:25 PM, 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 bytes. This
Hi!
If-conversion can't easily predict whether outer loop vectorization will be
successful or not. In GCC 6, we'd version and guard with LOOP_VECTORIZED
only the inner loop, which is beneficial if the outer loop vectorization
isn't successful, but inner loop vectorization is.
This changed last ye
On Fri, Jan 06, 2017 at 12:34:01PM -0500, David Malcolm wrote:
> On Fri, 2017-01-06 at 10:25 -0700, Jeff Law wrote:
> > On 01/06/2017 09:43 AM, David Malcolm wrote:
> > > On Fri, 2017-01-06 at 17:25 +0100, Jakub Jelinek wrote:
> > > > On Thu, Jan 05, 2017 at 03:20:26PM -0500, David Malcolm wrote:
>
On Fri, Jan 06, 2017 at 05:58:05PM +0100, Christophe Lyon wrote:
> > Trying now:
> >
> > 2017-01-06 Jakub Jelinek
> >
> > * Makefile.in (CFLAGS, CPPFLAGS, LDFLAGS): Remove -fno-lto.
> > (NOLTO_FLAGS): New variable.
> > (ALL_CFLAGS): Use it.
> > * configure.ac (nol
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-7.1-b20170101.fr.po', h
Jeff Law writes:
> On 01/06/2017 09:08 AM, Mikael Pettersson wrote:
> > This fixes / works-around the wrong-code PR57583 on M68K, caused by
> > overflowing the 16-bit jump table offsets the backend uses.
> >
> > Ideally the backend should define CASE_VECTOR_SHORTEN_MODE, but that
> > AFAIK ne
Richard Sandiford schrieb:
Segher Boessenkool writes:
On Wed, Jan 04, 2017 at 04:39:36PM +0100, Georg-Johann Lay wrote:
Well, if it can be done in the back-end, then that's generally my strong
preference. And the blocker for LRA is that it doesn't support cc0,
hence LRA will require an almost
On 01/03/2017 05:04 PM, Martin Sebor wrote:
The -Wformat-length option warns about both overflow and truncation.
I had initially debated introducing two options, one for each of
the two kinds of problems, but decided to go with just one and
consider breaking it up based on feedback.
I feel that
1 - 100 of 111 matches
Mail list logo
