On 10/24/2017 12:24 PM, Richard Sandiford wrote:
Andrew MacLeod writes:
On 10/19/2017 04:22 PM, Richard Sandiford wrote:
Richard Sandiford writes:
Aldy Hernandez writes:
gcc/
* wide-int-print.cc (print_hex): Loop based on extract_uhwi.
Don't print any bits outside the p
On Thu, Oct 26, 2017 at 10:12 AM, Wilco Dijkstra wrote:
> GCC's default optimization level is -O0. Unfortunately unlike other
> compilers,
> GCC generates extremely inefficient code with -O0. It is almost unusable for
> low-level debugging or manual inspection of generated code. So a -O option
On Tue, Oct 24, 2017 at 3:10 PM, Ian Lance Taylor wrote:
> I merged trunk revision 254059 to the gccgo branch.
I've now merged trunk revision 254126.
Ian
On 10/21/2017 11:17 AM, Bernhard Reutner-Fischer wrote:
> On 21 October 2017 at 02:26, Damian Rouson
> wrote:
>>
>> Hi Richard,
>>
>> Attached is a revised patch that makes the downloading of Fortran
>> prerequisites optional via a new --no-fortran flag that can be passed to
>> contrib/download
On Wed, Oct 25, 2017 at 07:57:09PM -0400, Michael Meissner wrote:
> On Wed, Oct 25, 2017 at 11:41:24PM +, Joseph Myers wrote:
> > My only comment on this version is that the documentation in cpp.texi of
> > __FP_FAST_* should be updated to mention __FP_FAST_FMAF@var{n} and
> > __FP_FAST_FMAF@
Hi,
On Wed, Oct 25, 2017 at 10:26:46AM -0500, Will Schmidt wrote:
> 2017-10-25 Will Schmidt
>
> * gcc.target/powerpc/fold-vec-neg-char.c: New.
> * gcc.target/powerpc/fold-vec-neg-floatdouble.c: New.
> * gcc.target/powerpc/fold-vec-neg-int.c: New.
> * gcc.target/powerpc
LWG 2133 makes it a requirement for some of the algorithms to protect
against overlaoded comma operators. This does so, and adapts some
tests to verify it, using our iterator wrappers. Those wrappers have a
member oeprator, but that only handles the case where the iterator is
the left operand, so
On 10/26/2017 11:52 AM, Richard Sandiford wrote:
Martin Sebor writes:
/* The tree and const_tree overload templates. */
namespace wi
{
+ class unextended_tree
+ {
+ private:
+const_tree m_t;
+
+ public:
+unextended_tree () {}
Defining no-op ctors is quite dangerous and error-
Hi Will,
On Thu, Oct 26, 2017 at 05:13:38PM -0500, Will Schmidt wrote:
> * config/rs6000/rs6000.c: (rs6000_gimple_fold_builtin) Add support for
> gimple folding of vec_madd() intrinsics.
The colon goes after the closing parenthesis, and continuation lines
should not have extra inden
On 10/26/2017 01:17 PM, Pedro Alves wrote:
On 10/26/2017 07:54 PM, Martin Sebor wrote:
(...) in the general case, it is preferable to
declare each variable at the point where its initial value is known
(or can be computed) and initialize it on its declaration.
With that I fully agree, except
This patch adds an explicit conversion between type aliases.
Otherwise we can get a crash in the backend when GCC sees a
fold_convert_loc between two record types that the GCC backend appear
to be different. Adding the explicit conversion will insert a
VIEW_CONVERT_EXPR where needed. The test cas
Hi,
[PATCH, rs6000] (v2) Gimple folding for vec_madd()
Add support for gimple folding of the vec_madd() (vector multiply-add)
intrinsics. Per earlier feedback and education, this now includes
the addition of a "define_expand fmav8hi4" in altivec.md.
Testcase coverage is provided by the
On Thu, 2017-10-26 at 11:38 +0200, Richard Biener wrote:
> You can eventually keep the option, marking it as Ignore (like we do
> for options we remove but "keep" for backward compatibility). The
> diagnostic (as warning, given the option will be just ignored) could
> be emited from option process
Hi Carl,
On Mon, Oct 23, 2017 at 08:36:03AM -0700, Carl Love wrote:
> The mode attribute wd will not work
> for the define expand as the V16QI maps to "b" not "q". So I do need to
> have VSX_XXBR.
Why is that a problem? Why do you want to swap the order of the whole
vector instead of changing t
Hi!
The following testcase is miscompiled, because due to STV we end up
with a load from V2DFmode MEM for which get_pool_entry returns
a V1TImode vector. maybe_get_pool_constant doesn't have code
to handle mode differences between what get_pool_constant returns
and the requested mode. While it w
On Thu, 2017-10-26 at 12:35 -0600, Sandra Loosemore wrote:
> On 10/26/2017 11:47 AM, Gerald Pfeifer wrote:
> > Thanks you for fleshing this out, Jim!
> >
> > This looks fine to me (modula Sandra's note). Just a question:
> > would
> > we refer to GDB instead of gdb here? It feels a little in bet
I've committed this patch, intended for bare-metal nios2-elf targets
with custom linker scripts. In conjunction with section attributes, it
provides a way to tell GCC that an object is assigned to the low or high
32K memory regions so that it can be addressed via a signed 16-bit
offset from r0
I've committed this patch, which allows users to specify additional data
sections (beyond the normal small-data sections) where GP-relative
addressing can be used. It's intended for use on bare-metal nios2-elf
targets in conjunction with section attributes and a custom linker script.
-Sandra
iple hot/cold transitions found (bb 64)
+===GNAT BUG DETECTED======+
| 8.0.0 20171026 (experimental) [trunk revision 254096] (x86_64-suse-linux)
GCC error:|
| verify_flow_info failed |
It's the RTL basi
On 26/10/17 21:37 +0100, Jonathan Wakely wrote:
On 26/10/17 21:30 +0100, Jonathan Wakely wrote:
On 26/10/17 22:19 +0200, François Dumont wrote:
@@ -1232,7 +1232,7 @@ class Printer(object):
# Add a name using _GLIBCXX_BEGIN_NAMESPACE_CONTAINER.
def add_container(self, base, name, function):
On 26/10/17 21:30 +0100, Jonathan Wakely wrote:
On 26/10/17 22:19 +0200, François Dumont wrote:
@@ -1232,7 +1232,7 @@ class Printer(object):
# Add a name using _GLIBCXX_BEGIN_NAMESPACE_CONTAINER.
def add_container(self, base, name, function):
self.add_version(base, name, function)
-
On 26/10/17 22:19 +0200, François Dumont wrote:
@@ -1232,7 +1232,7 @@ class Printer(object):
# Add a name using _GLIBCXX_BEGIN_NAMESPACE_CONTAINER.
def add_container(self, base, name, function):
self.add_version(base, name, function)
-self.add_version(base + '__cxx1998::',
On 26/10/17 21:45 +0200, François Dumont wrote:
On 26/10/2017 19:09, Jonathan Wakely wrote:
On 26/10/17 18:55 +0200, Daniel Krügler wrote:
2017-10-26 7:51 GMT+02:00 François Dumont :
Hi
We once talk about rename the __cxx1998 namespace into
something less
C++98 biased. Here is the patch
Hi
When restoring versioned namespace feature I forgot to check for
the pretty printer tests which are now broken.
Here is the patch to fix those. Tested under Linux x86_64 normal
and versioned namepace modes, ok to commit ?
François
diff --git a/libstdc++-v3/python/libstdcxx/v6/pr
On 26.10.2017 21:43, Kamil Rytarowski wrote:
> Tested on:
>
> $ uname -rms
> NetBSD 8.99.4 amd64
>
I forgot to amend everything in this patch, will fix in -v3.
signature.asc
Description: OpenPGP digital signature
Tested on:
$ uname -rms
NetBSD 8.99.4 amd64
The NetBSD support has been developed directly in the compiler-rt upstream
source.
Testing against the LLVM+Clang+compiler-rt (2017-10-25 snapshot from HEAD):
$ make check-asan
Failing Tests (2):
AddressSanitizer-Unit ::
./Asan-x86_64-calls-Test/
Tested on:
$ uname -rms
NetBSD 8.99.4 amd64
The NetBSD support has been developed directly in the compiler-rt upstream
source.
Testing against the LLVM+Clang+compiler-rt (2017-10-25 snapshot from HEAD):
$ make check-asan
Failing Tests (2):
AddressSanitizer-Unit ::
./Asan-x86_64-calls-Test/
On Thu, Oct 26, 2017 at 05:12:40PM +, Wilco Dijkstra wrote:
> GCC's default optimization level is -O0. Unfortunately unlike other
> compilers,
> GCC generates extremely inefficient code with -O0. It is almost unusable for
> low-level debugging or manual inspection of generated code. So a -O
> GCC's default optimization level is -O0. Unfortunately unlike other
> compilers, GCC generates extremely inefficient code with -O0.
Agreed (but this can probably be worked on).
> It is almost unusable for low-level debugging or manual inspection of
> generated code.
Likewise.
> So a -O opti
On 26/10/2017 19:09, Jonathan Wakely wrote:
On 26/10/17 18:55 +0200, Daniel Krügler wrote:
2017-10-26 7:51 GMT+02:00 François Dumont :
Hi
We once talk about rename the __cxx1998 namespace into something
less
C++98 biased. Here is the patch to do so.
Ok with the new name ?
IMO the
On Thu, Oct 26, 2017 at 02:43:55PM +0200, Richard Biener wrote:
> On Thu, Oct 26, 2017 at 2:18 PM, Richard Sandiford
> wrote:
> > Richard Biener writes:
> >> On Mon, Oct 23, 2017 at 1:22 PM, Richard Sandiford
> >> wrote:
> >>> This patch adds a POD version of fixed_size_mode. The only current u
Richard Biener writes:
> On Thu, Oct 26, 2017 at 2:18 PM, Richard Sandiford
> wrote:
>> Richard Biener writes:
>>> On Mon, Oct 23, 2017 at 1:22 PM, Richard Sandiford
>>> wrote:
This patch adds a POD version of fixed_size_mode. The only current use
is for storing the __builtin_apply a
> Can you figure what oldest GCC release supports the C++11/14 POD handling
> that would be required?
GCC needs to be buildable by other compilers than itself though.
--
Eric Botcazou
On Thu, Oct 26, 2017 at 09:24:58PM +0200, Kamil Rytarowski wrote:
> On 26.10.2017 21:19, Jakub Jelinek wrote:
> > On Thu, Oct 26, 2017 at 09:02:25PM +0200, Kamil Rytarowski wrote:
> >> 2017-10-26 Kamil Rytarowski
> >>
> >>* sanitizer_common/Makefile.am (sanitizer_common_files): Add
> >>s
On 26.10.2017 21:19, Jakub Jelinek wrote:
> On Thu, Oct 26, 2017 at 09:02:25PM +0200, Kamil Rytarowski wrote:
>> 2017-10-26 Kamil Rytarowski
>>
>> * sanitizer_common/Makefile.am (sanitizer_common_files): Add
>> sanitizer_platform_limits_netbsd.cc.
>> * sanitizer_common/Makefile.in
Hi Paul,
Without having tested the patch, it looks reasonable to me. So ok from my side.
- Andre
Am 26. Oktober 2017 21:12:45 MESZ schrieb Paul Richard Thomas
:
>Dear All,
>
>Thanks to Dimitry Liakh for both reporting the problem and doing a lot
>of the diagnostic work. Once the offending line
On Thu, Oct 26, 2017 at 09:02:25PM +0200, Kamil Rytarowski wrote:
> 2017-10-26 Kamil Rytarowski
>
> * sanitizer_common/Makefile.am (sanitizer_common_files): Add
> sanitizer_platform_limits_netbsd.cc.
> * sanitizer_common/Makefile.in: Regenerated.
Why is this needed?
libsaniti
On 10/26/2017 07:54 PM, Martin Sebor wrote:
> (...) in the general case, it is preferable to
> declare each variable at the point where its initial value is known
> (or can be computed) and initialize it on its declaration.
With that I fully agree, except it's not always possible or
natural. The
2017-10-26 Kamil Rytarowski
* sanitizer_common/Makefile.am (sanitizer_common_files): Add
sanitizer_platform_limits_netbsd.cc.
* sanitizer_common/Makefile.in: Regenerated.
---
libsanitizer/ChangeLog| 6 ++
libsanitizer/sanitizer_common/Makefile.am
Dear All,
Thanks to Dimitry Liakh for both reporting the problem and doing a lot
of the diagnostic work. Once the offending line in a very complicated
code was located, the fix was trivial. Generating a reduced testcase
took rather longer :-)
The comment in the testcase tells the story. The fix i
On 10/26/2017 12:05 PM, Pedro Alves wrote:
On 10/26/2017 05:37 PM, Martin Sebor wrote:
I agree that the latter use case is more common in GCC, but I don't
see it as a good thing. GCC was written in C and most code still
uses now outdated C practices such as declaring variables at the top
of a
On 10/26/2017 11:47 AM, Gerald Pfeifer wrote:
On Wed, 25 Oct 2017, Jim Wilson wrote:
The current documentation doesn't explain what the option is for, or
how one might use it. The attached patch expands the documentation a
bit to try to explain this.
OK?
Thanks you for fleshing this out, J
On 10/26/2017 02:12 PM, Eric Gallager wrote:
On 10/26/17, Nathan Sidwell wrote:
On 10/26/2017 10:34 AM, David Malcolm wrote:
Possibly a silly question, but is it OK to have a formatted string
call in which some of the arguments aren't consumed? (here "col" is only
consumed for the true case,
Hello Olga, Sebastian,
On 20 Oct 08:36, Peryt, Sebastian wrote:
> Hi,
>
> This patch written by Olga Makhotina adds listed below missing intrinsics:
> _mm512_[mask_]cmpeq_[pd|ps]_mask
> _mm512_[mask_]cmple_[pd|ps]_mask
> _mm512_[mask_]cmplt_[pd|ps]_mask
> _mm512_[mask_]cmpneq_[pd|ps]_mask
> _mm512
On 10/26/17, Wilco Dijkstra wrote:
> GCC's default optimization level is -O0. Unfortunately unlike other
> compilers,
> GCC generates extremely inefficient code with -O0. It is almost unusable
> for
> low-level debugging or manual inspection of generated code. So a -O option
> is
> always requi
On 10/26/17, Nathan Sidwell wrote:
> On 10/26/2017 10:34 AM, David Malcolm wrote:
>> [CCing Rainer and Mike for the gcc-dg.exp part]
>
>> Alternate idea: could show_column become a tri-state:
>>* default: show non-zero columns
>>* never: never show columns
>>* always: always show a col
On October 26, 2017 6:50:15 PM GMT+02:00, Jeff Law wrote:
>On 10/26/2017 03:24 AM, Richard Biener wrote:
>> On Tue, Oct 24, 2017 at 8:44 PM, Jeff Law wrote:
>>> This is similar to the introduction of the ssa_propagate_engine, but
>for
>>> the substitution/replacements bits.
>>>
>>> In a couple pl
On 10/26/2017 05:37 PM, Martin Sebor wrote:
> I agree that the latter use case is more common in GCC, but I don't
> see it as a good thing. GCC was written in C and most code still
> uses now outdated C practices such as declaring variables at the top
> of a (often long) function, and usually wit
Martin Sebor writes:
>> /* The tree and const_tree overload templates. */
>> namespace wi
>> {
>> + class unextended_tree
>> + {
>> + private:
>> +const_tree m_t;
>> +
>> + public:
>> +unextended_tree () {}
>
> Defining no-op ctors i
On Wed, 25 Oct 2017, Jim Wilson wrote:
> The current documentation doesn't explain what the option is for, or
> how one might use it. The attached patch expands the documentation a
> bit to try to explain this.
> OK?
Thanks you for fleshing this out, Jim!
This looks fine to me (modula Sandra's
On Wed, Oct 25, 2017 at 07:11:07PM -0500, Segher Boessenkool wrote:
> Hi Mike,
>
> On Sat, Oct 21, 2017 at 09:09:58AM -0400, Michael Meissner wrote:
> > As Segher and I were discussing off-line, I have some problems with the
> > current
> > -mabi={ieee,ibm}longdouble switches as we start to plann
This one.
https://gcc.gnu.org/ml/gcc-patches/2017-10/msg00537.html
There was discussion about documenting this, but the actual configure
change hasn't been reviewed yet.
-Sandra
GCC's default optimization level is -O0. Unfortunately unlike other compilers,
GCC generates extremely inefficient code with -O0. It is almost unusable for
low-level debugging or manual inspection of generated code. So a -O option is
always required for compilation. -Og not only allows for fast
On 26/10/17 18:55 +0200, Daniel Krügler wrote:
2017-10-26 7:51 GMT+02:00 François Dumont :
Hi
We once talk about rename the __cxx1998 namespace into something less
C++98 biased. Here is the patch to do so.
Ok with the new name ?
IMO the name should somehow still contain "cxx" somewhe
On 10/25/2017 06:26 PM, Jim Wilson wrote:
Index: gcc/doc/invoke.texi
===
--- gcc/doc/invoke.texi (revision 254023)
+++ gcc/doc/invoke.texi (working copy)
@@ -6981,7 +6981,12 @@ link processing time. Merging is enabled by defau
@it
2017-10-26 7:51 GMT+02:00 François Dumont :
> Hi
>
> We once talk about rename the __cxx1998 namespace into something less
> C++98 biased. Here is the patch to do so.
>
> Ok with the new name ?
IMO the name should somehow still contain "cxx" somewhere, otherwise
this could easily cause a s
On 10/26/2017 03:24 AM, Richard Biener wrote:
> On Tue, Oct 24, 2017 at 8:44 PM, Jeff Law wrote:
>> This is similar to the introduction of the ssa_propagate_engine, but for
>> the substitution/replacements bits.
>>
>> In a couple places the pass specific virtual functions are just wrappers
>> arou
The documentation for the "-mabi" argument on RISC-V was incorrect. We
chose to treat this as a documentation bug rather than a code bug, and
to make the documentation match what GCC currently does. In the
process, I also improved the documentation a bit.
Thanks to Alex Bradbury for finding the
/* The tree and const_tree overload templates. */
namespace wi
{
+ class unextended_tree
+ {
+ private:
+const_tree m_t;
+
+ public:
+unextended_tree () {}
Defining no-op ctors is quite dangerous and error-prone. I suggest
to instead default initialize the member(s):
unexte
On 10/26/2017 01:21 AM, Martin Liška wrote:
On 10/20/2017 06:03 AM, Sandra Loosemore wrote:
On 10/19/2017 12:26 PM, Eric Gallager wrote:
On 10/19/17, Martin Liška wrote:
Hi.
As discussed in the PR, we should be more precise in our documentation.
The patch does that.
Ready for trunk?
Martin
On 26/10/17 19:23 +0300, Ville Voutilainen wrote:
On 26 October 2017 at 18:04, Jonathan Wakely wrote:
Also, please put the deduction guides for a class immediately after
the definition of that class, rather than grouping all the guides for
unordered_map and unordered_multimap together.
Alrig
On 26 October 2017 at 18:04, Jonathan Wakely wrote:
> Also, please put the deduction guides for a class immediately after
> the definition of that class, rather than grouping all the guides for
> unordered_map and unordered_multimap together.
Alright.
2017-10-26 Ville Voutilainen
Deduct
On Fri, Aug 04, 2017 at 01:26:15PM +0100, Wilco Dijkstra wrote:
> The current frame code combines the separate concepts of a frame chain
> (saving old FP,LR in a record and pointing new FP to it) and a frame
> pointer used to access locals. Add emit_frame_chain to the aarch64_frame
> descriptor an
On 10/26/2017 03:09 AM, Richard Biener wrote:
> On Wed, Oct 25, 2017 at 5:44 PM, Jeff Law wrote:
>> On 10/24/2017 11:35 AM, Martin Sebor wrote:
>>> On 10/23/2017 05:14 PM, Jeff Law wrote:
Martin,
I'd like your thoughts on this patch.
One of the things I'm working on i
On Wed, 2017-10-25 at 18:37 -0500, Segher Boessenkool wrote:
> Hi!
>
> On Tue, Oct 17, 2017 at 01:27:16PM -0500, Steven Munroe wrote:
> > This it part 2/2 for contributing PPC64LE support for X86 SSE2
> > instrisics. This patch includes testsuite/gcc.target tests for the
> > intrinsics included by
On Fri, Jul 07, 2017 at 12:28:11PM +0100, Wilco Dijkstra wrote:
> This patch further improves aarch64_legitimate_constant_p. Allow all
> integer, floating point and vector constants. Allow label references
> and non-anchor symbols with an immediate offset. This allows such
> constants to be rema
The following fixes lower_eh_dispatch destroying dominator info
that was still live from previous passes. This clears it from the
obvious place (when we think we might have created unreachable blocks).
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
Richard.
2017-10-26 Richard
On Thu, 2017-10-26 at 17:18 +0200, Richard Biener wrote:
> On Thu, Oct 26, 2017 at 5:13 PM, Richard Biener
> wrote:
> > On Thu, Oct 26, 2017 at 4:30 PM, Will Schmidt
> > wrote:
> >> On Thu, 2017-10-26 at 11:05 +0200, Richard Biener wrote:
> >>> On Wed, Oct 25, 2017 at 4:38 PM, Will Schmidt
> >
On Thu, Oct 26, 2017 at 4:55 PM, Jeff Law wrote:
> On 10/17/2017 06:04 AM, Wilco Dijkstra wrote:
>> Wilco Dijkstra wrote:
>>>
>>> Yes STACK_BOUNDARY applies to virtual_stack_dynamic_rtx and all other
>>> virtual frame registers. It appears it's main purpose is to enable alignment
>>> optimizations
On Tue, Jul 25, 2017 at 02:58:04PM +0100, Wilco Dijkstra wrote:
> This patch makes some changes to the frame layout in order to simplify
> stack probing. We want to use the save of LR as a probe in any non-leaf
> function. With shrinkwrapping we may only save LR before a call, so it
> is useful t
On Thu, Oct 26, 2017 at 5:13 PM, Richard Biener
wrote:
> On Thu, Oct 26, 2017 at 4:30 PM, Will Schmidt
> wrote:
>> On Thu, 2017-10-26 at 11:05 +0200, Richard Biener wrote:
>>> On Wed, Oct 25, 2017 at 4:38 PM, Will Schmidt
>>> wrote:
>>> > Hi,
>>> >
>>> > Add support for gimple folding of the v
On Thu, Oct 26, 2017 at 4:30 PM, Will Schmidt wrote:
> On Thu, 2017-10-26 at 11:05 +0200, Richard Biener wrote:
>> On Wed, Oct 25, 2017 at 4:38 PM, Will Schmidt
>> wrote:
>> > Hi,
>> >
>> > Add support for gimple folding of the vec_madd() (vector multiply-add)
>> > intrinsics.
>> > Testcase cove
On Thu, Jul 20, 2017 at 01:49:03PM +0100, Wilco Dijkstra wrote:
> In https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01125.html Jiong
> pointed out some addressing inefficiencies due to a recent change in
> regcprop (https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00775.html).
>
> This patch improves
On Thu, Oct 26, 2017 at 4:38 PM, Richard Biener
wrote:
> On Thu, Oct 26, 2017 at 2:55 PM, Jan Hubicka wrote:
>>> I think the limit should be on the number of generated copies and not
>>> the overall size of the structure... If the struct were composed of
>>> 32 individual chars we wouldn't want
On 26/10/17 15:36 +0100, Jonathan Wakely wrote:
On 17/10/17 22:48 +0300, Ville Voutilainen wrote:
Tested on Linux-PPC64. The debug mode fixes have been tested manually
and individually on Linux-x64.
2017-10-17 Ville Voutilainen
Deduction guides for associative containers, debug mode deduc
On 10/18/2017 10:59 AM, Egeyar Bagcioglu wrote:
> Hello,
>
> Test case "guality.exp=nrv-1.c" fails on aarch64. Optimizations reorder
> the instructions and cause the value of a variable to be checked before
> its first assignment. The following patch is moving the
> break point to the end of the f
On 10/17/2017 06:04 AM, Wilco Dijkstra wrote:
> Wilco Dijkstra wrote:
>>
>> Yes STACK_BOUNDARY applies to virtual_stack_dynamic_rtx and all other
>> virtual frame registers. It appears it's main purpose is to enable alignment
>> optimizations since PREFERRED_STACK_BOUNDARY is used to align
>> local
On 10/05/2017 03:16 AM, Richard Biener wrote:
> On Thu, Oct 5, 2017 at 1:07 AM, Jeff Law wrote:
>> On 10/04/2017 08:53 AM, Eric Botcazou wrote:
This seems like a SPARC target problem to me -- essentially it's
claiming a higher STACK_BOUNDARY than it really has.
>>>
>>> No, it is not, I
On 10/26/2017 10:34 AM, David Malcolm wrote:
[CCing Rainer and Mike for the gcc-dg.exp part]
Alternate idea: could show_column become a tri-state:
* default: show non-zero columns
* never: never show columns
* always: always show a column, printing 0 for the no-column case
and then us
On Thu, Oct 26, 2017 at 2:55 PM, Jan Hubicka wrote:
>> I think the limit should be on the number of generated copies and not
>> the overall size of the structure... If the struct were composed of
>> 32 individual chars we wouldn't want to emit 32 loads and 32 stores...
>>
>> I wonder how rep; mov
On 17/10/17 22:48 +0300, Ville Voutilainen wrote:
Tested on Linux-PPC64. The debug mode fixes have been tested manually
and individually on Linux-x64.
2017-10-17 Ville Voutilainen
Deduction guides for associative containers, debug mode deduction
guide fixes.
* include/bits/stl_algobase
[CCing Rainer and Mike for the gcc-dg.exp part]
On Thu, 2017-10-26 at 07:33 -0400, Nathan Sidwell wrote:
> On the modules branch, I'm starting to add location
> information. Line
> numbers don't really make sense when reporting errors reading a
> binary
> file, so I wanted to change the diagnos
On Thu, 2017-10-26 at 11:05 +0200, Richard Biener wrote:
> On Wed, Oct 25, 2017 at 4:38 PM, Will Schmidt
> wrote:
> > Hi,
> >
> > Add support for gimple folding of the vec_madd() (vector multiply-add)
> > intrinsics.
> > Testcase coverage is provided by the existing tests
> > gcc.target/powerpc/
Hi,
After r254010 we now add -gcolumn-info by default, that means the tests
in gcc.target/arm/require-pic-register-loc.c need adjusting to not expect
to see column zero.
That's the obvious fix, and just extends what Jakub did in r254010 so
I've applied it as r254106.
Thanks,
James
---
2017-10-
Hi,
On Thu, 26 Oct 2017, Martin Jambor wrote:
> > 35 bytes seems to be much - what is the code-size impact?
>
> I will find out and report on that. I need at least 32 bytes (four
> long ints) to fix imagemagick, where the problematic structure is:
Surely the final heuristic should look at the
On 10/26/2017 03:33 AM, Richard Biener wrote:
> On Wed, Oct 25, 2017 at 11:24 PM, Jim Wilson wrote:
>> We have no targets that emit SDB debug info by default. We dropped all
>> of the SVR3 Unix and embedded COFF targets a while ago. The only
>> targets that are still able to emit SDB debug info
On Tue, Oct 24, 2017 at 10:47:32PM +0100, Michael Collison wrote:
> James,
>
> The patch was test as required. However when I tested with the latest trunk
> there were two test failures that need to be updated because of my patch.
>
> The files gcc.target/aarch64/vect-vcvt.c was failing because
On 26/09/17 00:25, Steve Ellcey wrote:
> This is a new version of my patch to fix PR target/79868, where some
> error messages are impossible to translate correctly due to how the
> strings are dynamically constructed. It also includes some format
> changes in the error messags to make the message
> I think the limit should be on the number of generated copies and not
> the overall size of the structure... If the struct were composed of
> 32 individual chars we wouldn't want to emit 32 loads and 32 stores...
>
> I wonder how rep; movb; interacts with store to load forwarding? Is
> that ma
On 10/25/2017 05:36 PM, Nathan Sidwell wrote:
This patch removes 'label_value' from lang_identifier, shrinking it from
72 to 64 bytes (on 64-bit machine). We replace this by augmenting the
already used per-function named_labels hash table. This is a major win,
because labels are extremely ra
On Thu, Oct 26, 2017 at 2:18 PM, Richard Sandiford
wrote:
> Richard Biener writes:
>> On Mon, Oct 23, 2017 at 1:22 PM, Richard Sandiford
>> wrote:
>>> This patch adds a POD version of fixed_size_mode. The only current use
>>> is for storing the __builtin_apply and __builtin_result register mode
On Thu, Oct 26, 2017 at 2:18 PM, Martin Jambor wrote:
> Hi,
>
> On Tue, Oct 17, 2017 at 01:34:54PM +0200, Richard Biener wrote:
>> On Fri, Oct 13, 2017 at 6:13 PM, Martin Jambor wrote:
>> > Hi,
>> >
>> > I'd like to request comments to the patch below which aims to fix PR
>> > 80689, which is an
On Mon, Oct 23, 2017 at 1:28 PM, Richard Sandiford
wrote:
> This patch avoids some calculations of the form:
>
> GET_MODE_SIZE (vector_mode) / GET_MODE_SIZE (element_mode)
>
> in simplify-rtx.c. If we're dealing with CONST_VECTORs, it's better
> to use CONST_VECTOR_NUNITS, since that remains co
On Thu, Oct 26, 2017 at 2:06 PM, Richard Biener
wrote:
> On Mon, Oct 23, 2017 at 1:25 PM, Richard Sandiford
> wrote:
>> This patch adds a stub helper routine to provide the mode
>> of a scalar shift amount, given the mode of the values
>> being shifted.
>>
>> One long-standing problem has been to
On Thu, Oct 26, 2017 at 2:23 PM, Richard Biener
wrote:
> On Mon, Oct 23, 2017 at 1:20 PM, Richard Sandiford
> wrote:
>> Similarly to the VEC_DUPLICATE_{CST,EXPR}, this patch adds two
>> tree code equivalents of the VEC_SERIES rtx code. VEC_SERIES_EXPR
>> is for non-constant inputs and is a norma
On Mon, Oct 23, 2017 at 1:20 PM, Richard Sandiford
wrote:
> Similarly to the VEC_DUPLICATE_{CST,EXPR}, this patch adds two
> tree code equivalents of the VEC_SERIES rtx code. VEC_SERIES_EXPR
> is for non-constant inputs and is a normal tcc_binary. VEC_SERIES_CST
> is a tcc_constant.
>
> Like VEC
On 10/24/2017 04:39 PM, Jason Merrill wrote:
> On 10/18/2017 08:48 AM, Martin Liška wrote:
>> This is second patch that addresses test-suite fallout. All these tests fail
>> because -Wreturn-type is
>> now on by default.
>
>> +++ b/gcc/testsuite/g++.dg/cpp0x/constexpr-diag3.C
>> -constexpr T g(T
Richard Biener writes:
> On Mon, Oct 23, 2017 at 1:22 PM, Richard Sandiford
> wrote:
>> This patch adds a POD version of fixed_size_mode. The only current use
>> is for storing the __builtin_apply and __builtin_result register modes,
>> which were made fixed_size_modes by the previous patch.
>
>
Hi,
On Tue, Oct 17, 2017 at 01:34:54PM +0200, Richard Biener wrote:
> On Fri, Oct 13, 2017 at 6:13 PM, Martin Jambor wrote:
> > Hi,
> >
> > I'd like to request comments to the patch below which aims to fix PR
> > 80689, which is an instance of a store-to-load forwarding stall on
> > x86_64 CPUs i
On Mon, Oct 23, 2017 at 1:30 PM, Richard Sandiford
wrote:
> store_info and read_info_type in dse.c represented the ranges as
> start/end, but a lot of the internal code used offset/width instead.
> Using offset/width throughout fits better with the poly_int.h
> range-checking functions.
Ok.
Rich
1 - 100 of 142 matches
Mail list logo
