On Sat, May 20, 2017 at 11:27 AM, Marc Glisse wrote:
> Hello,
>
> as asked, I am adding some replacement in match.pd instead of just deleting
> this (redundant with CCP). It is not clear how general the match.pd version
> needs to be. (for instance it could handle some casts in addition to what I
> What can I do to expedite the process? This currently holds the 8.0
> release, and I'm uneasy to be the culprit.
The way I usually do it is grab the commit in GCC, and apply it
as is in the GDB repository. To make it easier, I use the git
mirror of the GCC repository, because I can then just ad
This patch by Than McIntosh fixes the Go frontend to consistent mark
array pointers as l-values when an array index expression is used in
an l-value context. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
==
Please try this patch:
Index: config.in
===
--- config.in (revision 248482)
+++ config.in (working copy)
@@ -76,12 +76,16 @@
#undef HAVE_DECL_SBRK
/* Define to 1 if you have the declaration of `snprintf', and to 0 if you
On 25/05/2017 18:28, Jonathan Wakely wrote:
On 15/05/17 19:57 +0200, François Dumont wrote:
Hi
Following what I have started on RbTree here is a patch to default
implementation of default and move constructors on std::vector.
As in _Rb_tree_impl the default allocator is not value initi
On 05/26/2017 01:59 PM, David Malcolm wrote:
Ping:
https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00334.html
On Thu, 2017-05-04 at 14:16 -0400, David Malcolm wrote:
As of r247522, fix-it-hints can suggest the insertion of new lines.
This patch updates -Wimplicit-fallthrough to provide suggest
Ping:
https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00334.html
On Thu, 2017-05-04 at 14:16 -0400, David Malcolm wrote:
> As of r247522, fix-it-hints can suggest the insertion of new lines.
>
> This patch updates -Wimplicit-fallthrough to provide suggestions
> with fix-it hints, showing the user
I'd like to ping the following patches:
[PATCH 1/3] c-family: add name_hint/deferred_diagnostic
https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00439.html
[PATCH 2/3] C++: provide macro used-before-defined hint (PR c++/72786).
https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00437.html
Ping:
https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00321.html
On Thu, 2017-05-04 at 12:36 -0400, David Malcolm wrote:
> As of r247522, fix-it-hints can suggest the insertion of new lines.
>
> This patch uses this to implement a new "maybe_add_include_fixit"
> function in c-common.c and uses it
On Wed, 2017-05-03 at 09:51 -0400, David Malcolm wrote:
> On Thu, 2017-04-27 at 23:03 +0200, Marek Polacek wrote:
> > On Thu, Apr 27, 2017 at 05:10:24PM -0400, David Malcolm wrote:
> > > + /* First try const_cast. */
> > > + trial = build_const_cast (dst_type, orig_expr, 0 /* complain
> > > */);
Ping
On Fri, 2017-04-28 at 18:09 -0400, David Malcolm wrote:
> Ping for these two patches:
> - https://gcc.gnu.org/ml/gcc-patches/2017-03/msg00909.html
> - https://gcc.gnu.org/ml/gcc-patches/2017-03/msg00910.html
>
> On Thu, 2017-03-16 at 21:51 -0400, David Malcolm wrote:
> > It's possible to
Thanks to Alexey Neyman for reminding me that I've had this patch
outstanding in my tree for two months.
Re-tested and committed.
r~
* config/alpha/t-alpha (CRTSTUFF_T_CFLAGS): New.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@248522
138bc75d-0d04-0410-961f-82ee72b054a4
---
libgc
Hi,
This patch fixes a few issues in documentation of -mcx16 x86 backend option:
- remove implementor-speak ('oword')
- mention alignment restriction and availability only in 64-bit mode
- improve usage example
existing documentation uses a really silly example (128-bit integer
counters),
On Fri, May 26, 2017 at 7:44 AM, Ian Lance Taylor wrote:
> On Thu, May 25, 2017 at 1:31 PM, Max Filippov wrote:
>> On Thu, May 25, 2017 at 11:24 AM, augustine.sterl...@gmail.com
>> wrote:
>>
>>> Please note that by using a plugin mechanism, there are licensing
>>> issues that come into play, tha
On Fri, May 26, 2017 at 9:08 AM, Iain Buclaw wrote:
> This is instead of adding a `.init$' postfix, which gave it a
> property-style name. My rationale being that "initializer for symbol"
> is much more informative when inspecting D runtime type information in
> gdb, which is the only place where
On Fri, May 26, 2017 at 8:49 AM, Iain Buclaw wrote:
> In the normal case, functions are passed around as a
> pointer-to-function type. One place where this is not the case
> however is when a function appears in template arguments, here the
> function is instead passed by alias.
>
> This patch up
On Fri, May 26, 2017 at 8:48 AM, Iain Buclaw wrote:
>
> This patch fixes a problem in the D demangler where an abnormally long
> mangled floating point literal would cause the program write past the
> allocated stack buffer. This should never happen with a valid D
> symbol, but we should be able
DR2061 concerns the meaning of:
inline namespace One {
namespace Term { }
}
namespace Term {
}
Does that second Term open a new namespace inside :: or reopen ::One::Term?
DR2061 resolves to ::One::Term -- i.e. the lookup considers inline
namespaces.
This patch implements that behaviour. r
Hi,
I missed the DWARF-5 deadline so I have submitted this for DWARF-6
(not yet on http://dwarfstd.org ):
--
.gdb_index contained an attribute for each symbol whether it is DW_AT_external
or not.
/* Whether the symbol is
Joel Brobecker writes:
> Normally, I'd expect someone pushing to GCC's libibert to also
> update our repo accordingly.
Note that I used to auto-sync libiberty from gcc to binutils/gdb, but
when binutils/gdb switched to git, that script broke, and as I don't
like using git, I announced that I wou
> Date: Fri, 26 May 2017 09:30:53 -0700
> From: Joel Brobecker
> Cc: DJ Delorie , gcc-patches@gcc.gnu.org,
> gdb-patc...@sourceware.org
>
> Normally, I'd expect someone pushing to GCC's libibert to also
> update our repo accordingly. However, it's easy to forget so,
> if you notice a change
This patch changes the representation of a namespace's inline children
and using directives.
Using directive were a TREE_LIST, which (a) held the complete graph and
(b) noted the common ancestor. We now need neither of them
Inline children were in the using directive list too, but then I
st
Hello world,
I have committed the attached patch as obvious as r248519 after testing
that it does indeed work on powerpc64-unknown-linux-gnu and that
it passes regression-test on that machine.
Sorry for the breakage. I'll use the gcc compile farm machines
in the future to test any such changes.
Hi,
This test has been flaky on both AIX and in older linux based
environments. Notably, the number of xxlor instructions
generated varies depending on the platform and the specified
bit-size (32/64), with older environments generating either 6 or 24
xxlor instructions. The behavior appears to l
Hi,
Add support for early expansion of vector shifts. Including
vec_sl (shift left), vec_sr (shift right), vec_sra (shift
right algebraic), vec_rl (rotate left).
Part of this includes adding the vector shift right instructions to
the list of those instructions having an unsigned second argument.
Hi,
Add support for early expansion of vector eqv built-ins.
Bootstraps currently running.
OK for trunk?
Thanks,
-Will
[gcc]
2017-05-26 Will Schmidt
* config/rs6000/rs6000.c (rs6000_gimple_fold_builtin): Add handling
for early expansion of vec_eqv.
Hi,
Add support for early expansion of vector absolute built-ins.
Bootstraps currently running (p7,p8le,p8be).
OK for trunk?
Thanks,
-Will
[gcc]
2017-05-26 Will Schmidt
* config/rs6000/rs6000.c (rs6000_gimple_fold_builtin): Add handling
for early expansion of vector absolute bu
Hi,
Add support for early expansion of vec_min, vec_max built-ins.
Bootstraps currently running.
OK for trunk?
Thanks,
-Will
[gcc]
2017-05-26 Will Schmidt
* config/rs6000/rs6000.c (rs6000_gimple_fold_builtin): Add handling
for early expansion of vec_min and vec_max builtin
We have a funky combined lookup & ADL, called exactly twice to find
operator new. Let's break that apart to separate lookups for clarity.
struct scope_binding is now dead, having been consumed by name_lookup.
A stale declaration of do_using_directive was still there and confused
libcp1plugin
> Thanks. Is the environ thing also fixed?
>
> Joel/Pedro, how should I go about making sure these changes are in the
> GDB copy of libiberty?
Normally, I'd expect someone pushing to GCC's libibert to also
update our repo accordingly. However, it's easy to forget so,
if you notice a change that
GCC Maintainers:
This is version 2 of the patch to add support for the various
vec_doublee, vec_doubleo, vec_doublel, vec_doubleh builtin-ins. I have
addressed the various comments from Segher.
The patch has been tested on powerpc64le-unknown-linux-gnu (Power 8 LE)
with no regressions.
Is the pa
This is instead of adding a `.init$' postfix, which gave it a
property-style name. My rationale being that "initializer for symbol"
is much more informative when inspecting D runtime type information in
gdb, which is the only place where you would encounter references to
this compiler-generated sy
In the normal case, functions are passed around as a
pointer-to-function type. One place where this is not the case
however is when a function appears in template arguments, here the
function is instead passed by alias.
This patch updates dlang_type() to handle this case.
---
commit 43a0c37b48f8
Hi,
This patch fixes a problem in the D demangler where an abnormally long
mangled floating point literal would cause the program write past the
allocated stack buffer. This should never happen with a valid D
symbol, but we should be able to handle anything thrown at us.
---
commit 62d51a8de1fa
Bill Seurer pointed out that building the BMI tests on a power8 but with
gcc built --with-cpu=power6 fails with link errors. The intrinsics
_pdep_u64/32 and _pext_u64/32 are guarded with #ifdef _ARCH_PWR7 as the
implementation uses bpermd and popcntd instructions introduced with
power7 (PowerISA-2.
On 05/26/2017 12:41 AM, Andrew Pinski wrote:
On Thu, May 25, 2017 at 6:43 PM, Jerry DeLisle wrote:
On 05/25/2017 02:57 PM, Thomas Koenig wrote:
Hi everybody,
I have committed the patch (with the corrections for the name)
as rev 248472.
The infrastructure is in place, so we will be able to m
This patch enables the 2D nature of lookup results.
Previously whenever we had to combine overload sets from multiple
places, we'd prepend one of them, one function at a time, to the other.
This patch changes that. We can prepend an entire overload set as a
single entry to another set. This
Hello,
The attach patch (dup.diff) performs the following changes:
* bid/bid2dpd_dpd2bid.c: Remove identical code for different
branches (CID 1286836, 1286837, 1286838)
Remove some useless } else { declaration as we are returning
Remove some whitespace changes & tab
i
On Thu, May 25, 2017 at 1:31 PM, Max Filippov wrote:
> On Thu, May 25, 2017 at 11:24 AM, augustine.sterl...@gmail.com
> wrote:
>
>> Please note that by using a plugin mechanism, there are licensing
>> issues that come into play, that are different from the usual
>> licensing issues. I would be ab
d for you now.
Please let me know if it doesn't.
Brilliant, the gcc-6-branch builds cleanly for msp430-elf now, thanks!
-bash-4.2$ ./usr/local/bin/msp430-elf-gcc -v
Target: msp430-elf
Configured with: ../configure --target=msp430-elf --enable-languages=c,c++
Thread model: single
gcc version 6.3.1 20170526 (GCC)
[resending with gcc-patches this time]
Hi,
The comment describing ARM register allocation in arm.h contains 3 keys:
S, F and *. The legend only explains S and *, this patch remedies that.
ChangeLog entry is as follows:
*** gcc/ChangeLog ***
2017-05-24 Thomas Preud'homme
* config/a
Hi,
Name of arm_compute_save_reg_mask and thumb1_compute_save_reg_mask
suggest that all register saving computation is done in these function
but these only deal with core registers. The caller
arm_compute_frame_layout () also computes some of the register saving,
eg. for VFP registers in 32bit t
On Fri, May 26, 2017 at 12:15 PM, Richard Biener
wrote:
> On Tue, May 23, 2017 at 6:22 PM, Bin Cheng wrote:
>> Hi,
>> This is the second patch in the set, it factors out code pruning runtime
>> alias
>> checks from file tree-vect-data-refs.c to tree-data-ref.c. It also
>> introduces
>> new int
Hello,
Thanks for your suggestions, Jason.
On 05/08/2017 06:27 PM, Jason Merrill wrote:
That seems like a bug; if gen_typedef_die is going to generate a DIE
for a cloned typedef, it needs to associate the type with the DIE.
Hm… gen_typedef_die generates a DIE for a DECL node, but
modified_ty
On Fri, May 26, 2017 at 12:50 PM, Richard Biener
wrote:
> On Fri, May 26, 2017 at 1:30 PM, Bin.Cheng wrote:
>> On Fri, May 26, 2017 at 12:14 PM, Richard Biener
>> wrote:
>>> On Tue, May 23, 2017 at 6:22 PM, Bin Cheng wrote:
Hi,
This patch set factors out runtime alias check code from
Hi,
This patch most likely broke all non-x86 targets:
configure: error: conditional "HAVE_AVX128" was never defined.
Usually this means the macro was only invoked conditionally.
Makefile:19843: recipe for target 'configure-target-libgfortran' failed
make[1]: *** [configure-target-libgfortran] Erro
On 05/26/2017 02:31 PM, Richard Biener wrote:
> Well, then we have to go without the constructor. Runtime init isn't
> an option IMHO.
> Just use some macros for the eye candy, will you?
>
> Richard.
Yep. I'm testing following eye candy patch.
Ready to install after tests?
Martin
>From 5339db72
Hi!
[ please cc: me and David on rs6000 patches ]
On Wed, May 24, 2017 at 09:51:46AM +0200, Eric Botcazou wrote:
> this fixes an internal error with -fstack-limit-register and large frames:
>
> eric@polaris:~/build/gcc/powerpc-linux> gcc/xgcc -Bgcc -S stack-limit-1.c -
> fstack-limit-register=r2
On 05/26/2017 03:00 PM, Martin Liška wrote:
> Ok, sending new patch that does that on experimental branches for ${CC}
> --version
> being a GCC newer than 4.9.
s/4.9/4.8/
On 05/26/2017 01:55 PM, Richard Biener wrote:
> On Fri, May 26, 2017 at 1:51 PM, Jakub Jelinek wrote:
>> On Fri, May 26, 2017 at 01:46:47PM +0200, Richard Biener wrote:
>>> On Thu, May 25, 2017 at 11:23 AM, Martin Liška wrote:
Hello.
After a discussion with Richi, using adding "-O2
On Thu, May 25, 2017 at 11:52 AM, Martin Liška wrote:
> On 05/25/2017 05:35 AM, Martin Sebor wrote:
>> On 05/12/2017 07:04 AM, Martin Liška wrote:
>>> Third part removes TDF_* flags mentioned in the subject. These flags are
>>> used
>>> to enable all passes of specific type and Nathan has recentl
On Fri, May 26, 2017 at 1:59 PM, Bin.Cheng wrote:
> On Fri, May 26, 2017 at 12:39 PM, Richard Biener
> wrote:
>> On Thu, May 25, 2017 at 5:15 PM, Bin.Cheng wrote:
>>> On Wed, May 24, 2017 at 11:54 AM, Richard Sandiford
>>> wrote:
"Bin.Cheng" writes:
> On Tue, May 23, 2017 at 6:53 PM,
On Wed, May 24, 2017 at 6:04 PM, Richard Biener
wrote:
> On May 24, 2017 5:38:53 PM GMT+02:00, Andrew MacLeod
> wrote:
>>On 05/24/2017 04:25 AM, Richard Biener wrote:
>>> > What's this overflow flag for anyway?
>>
>>The new on-demand range calculators do operations on ranges, and that
>>flag is
On 22/05/17 17:16 +0100, Jozef Lawrynowicz wrote:
Ping, original post:
https://gcc.gnu.org/ml/gcc-patches/2017-03/msg01560.html
These are both libstdc++ patches and originally posted to the
libstdc++ list, so you'll have more luck mailing that list. I
committed both patches you're asking about,
On Fri, May 26, 2017 at 12:39 PM, Richard Biener
wrote:
> On Thu, May 25, 2017 at 5:15 PM, Bin.Cheng wrote:
>> On Wed, May 24, 2017 at 11:54 AM, Richard Sandiford
>> wrote:
>>> "Bin.Cheng" writes:
On Tue, May 23, 2017 at 6:53 PM, Richard Sandiford
wrote:
> AIUI, the reason the ol
On Fri, May 26, 2017 at 1:51 PM, Jakub Jelinek wrote:
> On Fri, May 26, 2017 at 01:46:47PM +0200, Richard Biener wrote:
>> On Thu, May 25, 2017 at 11:23 AM, Martin Liška wrote:
>> > Hello.
>> >
>> > After a discussion with Richi, using adding "-O2" to STAGE1 cflags with a
>> > recent
>> > enough
On Fri, May 26, 2017 at 01:46:47PM +0200, Richard Biener wrote:
> On Thu, May 25, 2017 at 11:23 AM, Martin Liška wrote:
> > Hello.
> >
> > After a discussion with Richi, using adding "-O2" to STAGE1 cflags with a
> > recent
> > enough compiler can significantly speed up bootstrap. Thus I'm sugges
On Wed, May 24, 2017 at 10:48 PM, Martin Liška wrote:
> Hi Richi.
>
> That's a small reminder. I CCed Steven, but I guess if the TDF_COMMENT would
> be really
> important, it can be eventually added back.
>
> May I install the patch now?
Ok.
Richard.
> Thanks,
> Martin
On Fri, May 26, 2017 at 1:30 PM, Bin.Cheng wrote:
> On Fri, May 26, 2017 at 12:14 PM, Richard Biener
> wrote:
>> On Tue, May 23, 2017 at 6:22 PM, Bin Cheng wrote:
>>> Hi,
>>> This patch set factors out runtime alias check code from
>>> tree-vect-data-refs.c
>>> and tree-vect-loop-manip.c as gen
On Thu, May 25, 2017 at 8:00 PM, Bin Cheng wrote:
> Hi,
> I believe this tests has been wrongly modified previously. It is to test
> that the exit check on
> pointer shouldn't be replaced by integer IV. Somehow GCC starts replacing
> the check on
> integer IV with pointer IV. It's valid, thou
On Fri, May 26, 2017 at 07:35:47AM -0400, Nathan Sidwell wrote:
> On 05/26/2017 03:54 AM, Jakub Jelinek wrote:
> > On Thu, May 25, 2017 at 09:03:31AM -0400, Nathan Sidwell wrote:
> > > This patch reimplements ADL.
>
> > I believe this broke
> > FAIL: libgomp.c++/udr-12.C (test for excess errors)
>
On Thu, May 25, 2017 at 7:58 PM, Bin Cheng wrote:
> Hi,
> Test gcc.target/i386/l_fma_double_1.c depends on how many times prolog/epilog
> loops are unrolled.
> This patch adapts the test strings in line with patch at
> https://gcc.gnu.org/ml/gcc-patches/2017-05/msg01689.html
>
> Bootstrap and te
On Thu, May 25, 2017 at 11:23 AM, Martin Liška wrote:
> Hello.
>
> After a discussion with Richi, using adding "-O2" to STAGE1 cflags with a
> recent
> enough compiler can significantly speed up bootstrap. Thus I'm suggesting to
> introduce --with-stage1-cflags where one can provide such options.
On Thu, May 25, 2017 at 5:15 PM, Bin.Cheng wrote:
> On Wed, May 24, 2017 at 11:54 AM, Richard Sandiford
> wrote:
>> "Bin.Cheng" writes:
>>> On Tue, May 23, 2017 at 6:53 PM, Richard Sandiford
>>> wrote:
AIUI, the reason the old code mishandled negative steps was that the
associated seg
Hurugalawadi, Naveen wrote:
>
> Please consider this as a personal reminder to review the patch
> at following link and let me know your comments on the same.
>
> https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01333.html
Looks good to me.
Wilco
On 05/26/2017 03:54 AM, Jakub Jelinek wrote:
On Thu, May 25, 2017 at 09:03:31AM -0400, Nathan Sidwell wrote:
This patch reimplements ADL.
I believe this broke
FAIL: libgomp.c++/udr-12.C (test for excess errors)
UNRESOLVED: libgomp.c++/udr-12.C compilation failed to produce executable
In ans
Hurugalawadi, Naveen wrote:
>
> Please consider this as a personal reminder to review the patch
> at following link and let me know your comments on the same.
>
> https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00839.htmll
That looks good to me now.
Wilco
On Fri, May 26, 2017 at 12:14 PM, Richard Biener
wrote:
> On Tue, May 23, 2017 at 6:22 PM, Bin Cheng wrote:
>> Hi,
>> This patch set factors out runtime alias check code from
>> tree-vect-data-refs.c
>> and tree-vect-loop-manip.c as general interfaces in tree-data-ref.c. With
>> this
>> change
On Tue, May 23, 2017 at 6:23 PM, Bin Cheng wrote:
> Hi,
> This is a simple patch changing parameter to below functions:
> create_intersect_range_checks_index
> create_intersect_range_checks
> as well as updating calls to these functions. This is to make
> them independent to vectorizer's data
On Tue, May 23, 2017 at 6:22 PM, Bin Cheng wrote:
> Hi,
> This is the second patch in the set, it factors out code pruning runtime alias
> checks from file tree-vect-data-refs.c to tree-data-ref.c. It also introduces
> new interface prune_runtime_alias_test_list so that we can use it in pass like
On Tue, May 23, 2017 at 6:22 PM, Bin Cheng wrote:
> Hi,
> This patch set factors out runtime alias check code from tree-vect-data-refs.c
> and tree-vect-loop-manip.c as general interfaces in tree-data-ref.c. With
> this
> change other optimizers like tree loop distribution could version loop wrt
Hello.
Unfortunately I guarded use-after-scope to track live switch variables just
to BIND_EXPR. However the bind expression can be included in a STATEMENT_LIST.
That enables proper tracking and fixes the test added.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Read
On Wed, 17 May 2017, Alexander Monakov wrote:
> Ping.
Ping^2?
> (to be clear, patch 2/2 is my previous followup in this thread, I forgot to
> adjust the subject line; it should have said:
> "[PATCH 2/2] x86: add compiler memory barriers when expanding atomic_load").
>
> On Wed, 10 May 2017, Ale
On Fri, May 26, 2017 at 12:39 PM, Marc Glisse wrote:
> On Fri, 26 May 2017, Richard Biener wrote:
>
>> On Fri, May 26, 2017 at 11:52 AM, Marc Glisse
>> wrote:
>>>
>>> Hello,
>>>
>>> coming back to https://gcc.gnu.org/ml/gcc-patches/2014-02/msg01378.html ,
>>> Richard wanted a complete set of fenv
On Fri, 26 May 2017, Richard Biener wrote:
On Fri, May 26, 2017 at 11:52 AM, Marc Glisse wrote:
Hello,
coming back to https://gcc.gnu.org/ml/gcc-patches/2014-02/msg01378.html ,
Richard wanted a complete set of fenv functions instead of just the 2 I was
interested in. However, most functions i
On Fri, May 26, 2017 at 11:52 AM, Marc Glisse wrote:
> Hello,
>
> coming back to https://gcc.gnu.org/ml/gcc-patches/2014-02/msg01378.html ,
> Richard wanted a complete set of fenv functions instead of just the 2 I was
> interested in. However, most functions in fenv.h handle a struch fenv_t or
> f
Hello,
coming back to https://gcc.gnu.org/ml/gcc-patches/2014-02/msg01378.html ,
Richard wanted a complete set of fenv functions instead of just the 2 I
was interested in. However, most functions in fenv.h handle a struch
fenv_t or fexcept_t, which makes them inconvenient to handle as builtins
Hi,
this patch replaces absolute line numbers in gcc.dg.
Committed.
Thanks,
- Tom
Replace absolute line numbers in gcc.dg
2017-05-24 Tom de Vries
PR testsuite/80557
* gcc.dg/20011021-1.c: Replace absolute line numbers.
* gcc.dg/Wcxx-compat-8.c: Same.
* gcc.dg/Wobjsize-1.c: Same.
* gcc
Hi,
This patch fixes these PR's. Ok for trunk?
gcc/
* config/i386/subst.md (round): Fix round pattern.
* config/i386/i386.c (ix86_erase_embedded_rounding):
Fix erasing rounding for the fixed pattern.
Thanks,
Julia
0001-patch_1.patch
Description: 0001-patch_1.patch
On Fri, May 26, 2017 at 10:55 AM, Marc Glisse wrote:
> Hello,
>
> glibc marks fegetround as a pure function. On x86, people tend to use
> _MM_GET_ROUNDING_MODE instead, which could benefit from the same. I think it
> is safe, but a second opinion would be welcome.
Sounds good. The important part
On Thu, May 25, 2017 at 6:33 PM, Marek Polacek wrote:
> We ICE on this testcase in
> 9812 /* Transform x * -C into -x * C if x is easily negatable. */
> 9813 if (TREE_CODE (op1) == INTEGER_CST
> 9814 && tree_int_cst_sgn (op1) == -1
> 9815 && neg
On Thu, May 25, 2017 at 5:05 PM, Mike Stump wrote:
> On May 24, 2017, at 1:25 AM, Richard Biener
> wrote:
>>
>> There's trailing_wide_ints. But having 6 of them is still expensive.
>>
>> Something nice would be to make wide_ints not tied to use HOST_WIDE_INT
>> as basic element type but for exa
Hello,
glibc marks fegetround as a pure function. On x86, people tend to use
_MM_GET_ROUNDING_MODE instead, which could benefit from the same. I think
it is safe, but a second opinion would be welcome.
I could have handled just this builtin, but it seemed better to provide
def_builtin_pure (
On Thu, May 25, 2017 at 12:00 PM, Martin Liška wrote:
> Hello.
>
> Having value of parameter partial-inlining-entry-probability bigger than 100
> does not
> make sense and can be just used to artificially trigger partial inlining.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regressio
> From: DJ Delorie
> Cc: gcc-patches@gcc.gnu.org, gdb-patc...@sourceware.org
> Date: Wed, 24 May 2017 17:36:16 -0400
>
> Thanks. Committed!
Thanks. Is the environ thing also fixed?
Joel/Pedro, how should I go about making sure these changes are in the
GDB copy of libiberty?
On Thu, May 25, 2017 at 09:03:31AM -0400, Nathan Sidwell wrote:
> This patch reimplements ADL.
>
> I replace the existing adl_lookup object with a new name_lookup object, and
> move all the workers into it as member fns.
>
> In terms of implementation, ADL requires us to look in a bunch of places
There's quite some instability in the lattice when match-and-simplify
is mixed with CCP. We deal with part of that already by meeting
with the old value in set_lattice_value, the following deals with this
new case by doing it always.
SSA propagation and match-and-simplify don't play well with ea
I noticed we keep the VF != 0 check in the CFG for quite some passes
when looking at PR80844 so the following fixes that.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2017-05-26 Richard Biener
PR tree-optimization/80844
* tree-vectorizer.c (adjust_s
88 matches
Mail list logo