On Tue, Feb 11, 2020 at 08:34:15AM +0100, Richard Biener wrote:
> On Mon, 10 Feb 2020, Segher Boessenkool wrote:
> > Yes, we should decide how often we want to unroll things somewhere before
> > ivopts already, and just use that info here.
> >
> > Or are there advantage to doing it *in* ivopts? I
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'cpplib' has been submitted
by the Chinese (traditional) team of translators. The file is available at:
https://translationproject.org/latest/cpplib/zh_TW.po
(This file, 'cp
cpplib-10.1-b20200209.zh_TW.po.gz
Description: Binary data
The Translation Project robot, in the
name of your translation coordinator.
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 Chinese (traditional) team of translators. The file is available at:
https://translationproject.org/latest/gcc/zh_TW.po
(This file, 'gcc-10.1
On Mon, 10 Feb 2020, Segher Boessenkool wrote:
> Hi!
>
> On Mon, Feb 10, 2020 at 02:17:04PM +0800, Kewen.Lin wrote:
> > on 2020/1/20 下午8:33, Segher Boessenkool wrote:
> > > On Thu, Jan 16, 2020 at 05:36:52PM +0800, Kewen.Lin wrote:
> > >> As we discussed in the thread
> > >> https://gcc.gnu.org/m
On 2/7/20 1:06 PM, Iain Sandoe wrote:
Hi,
This is the first of the (small number of) anticipated changes to bring
the implementation into line with the latest published C++20 draft (this
is now expected to be very close to the final, although some wording
might still be adjusted).
The allocatio
On Mon, Feb 10, 2020 at 10:22:37PM -0600, Bill Schmidt wrote:
> On 2/10/20 9:24 PM, Segher Boessenkool wrote:
> >>If you use -mpcrel, the compiler will generate PC-relative
> >>loads and stores to access items, rather than the current TOC based loads
> >>and
> >>stores.
> >Where that is the best t
Hi!
On Tue, Feb 11, 2020 at 02:50:03PM +0800, Kewen.Lin wrote:
> v3 changes:
> - Updated _uf to _unroll for some function names.
Thanks.
> By the way, should I guard the current i386/s390 loop_unroll_adjust
> ealy return with (current_pass->type != RTL_PASS)? I'm inclined not
> to, since this
Hi,
v3 changes:
- Updated _uf to _unroll for some function names.
By the way, should I guard the current i386/s390 loop_unroll_adjust
ealy return with (current_pass->type != RTL_PASS)? I'm inclined not
to, since this analysis isn't enabled by default, if those targets
want to adopt this analys
By making __glibcxx_assert constexpr compatible we can get rid of a
FIXME in basic_string_view and so fix following XPASS in _GLIBCXX_DEBUG
modes.
XPASS: 21_strings/basic_string_view/element_access/char/2.cc execution test
XPASS: 21_strings/basic_string_view/element_access/wchar_t/2.cc
executi
On 2/10/20 9:24 PM, Segher Boessenkool wrote:
Hi!
On Mon, Feb 10, 2020 at 01:45:42PM -0500, Michael Meissner wrote:
This patch renames the PowerPC internal switch -mprefixed-addr to be
-mprefixed.
If you use -mpcrel, you must be using the 64-bit ELF v2 ABI, and the code model
must be medium.
Hi!
On Mon, Feb 10, 2020 at 03:39:49PM -0600, will schmidt wrote:
> This adds a target_supports entry to check that the
> _ieee128 keyword is understood by the target.
(Two underscores, "__ieee128".)
> Also adds that require-effective-target check to the
> existing pr92796 testcase.
> +# See if
Hi!
On Mon, Feb 10, 2020 at 03:39:44PM -0600, will schmidt wrote:
> This fixes up a few tests that explicitly disable vsx,
> but still require altivec be enabled by adding the -maltivec
> option. (Noted on AIX, also seen on Linux/Power6).
> diff --git a/gcc/testsuite/gcc.target/powerpc/pr7
Hi!
On Mon, Feb 10, 2020 at 01:45:42PM -0500, Michael Meissner wrote:
> This patch renames the PowerPC internal switch -mprefixed-addr to be
> -mprefixed.
> If you use -mpcrel, you must be using the 64-bit ELF v2 ABI, and the code
> model
> must be medium.
Currently, anyway.
> If you use -mpcr
Hi Jeff,
on 2020/2/11 上午10:14, Jiufu Guo wrote:
> "Kewen.Lin" writes:
>
>> Hi Segher,
>>
>> Thanks for your comments! Updated to v2 as below:
>>
>> 1) Removed unnecessary hook loop_unroll_adjust_tree.
>> 2) Updated estimated_uf to estimated_unroll and some comments.
>>
>> gcc/ChangeLog
>>
>
on 2020/2/11 上午5:29, Segher Boessenkool wrote:
> Hi!
>
> On Mon, Feb 10, 2020 at 02:17:04PM +0800, Kewen.Lin wrote:
>> on 2020/1/20 下午8:33, Segher Boessenkool wrote:
>>> On Thu, Jan 16, 2020 at 05:36:52PM +0800, Kewen.Lin wrote:
As we discussed in the thread
https://gcc.gnu.org/ml/gcc-pa
Hi
As title. in maybe_promote_captured_temps, we promote captured temporaries
and co_await_expr into a new BIND_EXPR. As the BIND_EXPR contains
co_await_expr and maybe other function calls, the side effects flag should
be set.
This patch fix one mismatch in cppcoro, the testcase comes from cppcor
On Mon, Feb 10, 2020 at 07:07:46PM +0100, Jakub Jelinek wrote:
> We use sizeof ("...") - 1 or sizeof "..." - 1 in a lot of places though.
[...]
> config/rs6000/rs6000.c:spaces += sizeof (" Reload=sl") - 1;
> config/rs6000/rs6000.c:spaces += sizeof (" Upper=y") - 1;
> config/rs6000/rs600
It is easier to read and understand strlen ("string") than it is to
read and understrand sizeof ("string") - 1 .
Tested on powerpc64-linux {-m32,-m64}. Committing to trunk.
Segher
2020-02-10 Segher Boessenkool
* config/rs6000/rs6000.c (rs6000_debug_print_mode): Don't use sizeo
Jan Hubicka writes:
>> On Mon, 2020-02-03 at 10:04 -0600, Pat Haugen wrote:
>> > On 2/3/20 2:17 AM, Jiufu Guo wrote:
>> > > +/* { dg-final { scan-rtl-dump-times "REG_BR_PROB 937042044" 1
>> > > "loop2_unroll"} } */
>> >
>> > Sorry I didn't catch this addition to the original testcase
>> > earli
"Kewen.Lin" writes:
> Hi Segher,
>
> Thanks for your comments! Updated to v2 as below:
>
> 1) Removed unnecessary hook loop_unroll_adjust_tree.
> 2) Updated estimated_uf to estimated_unroll and some comments.
>
> gcc/ChangeLog
>
> 2020-02-10 Kewen Lin
>
> * cfgloop.h (struct loop):
Hi
In maybe_promote_captured_temps, the cleanup_point_stmt has been
stripped when handle temporaries captured by reference. However, maybe
there are non-reference temporaries in current stmt which cause ice in
gimpilify pass.
This patch fix this. The testcase comes from cppcoro and is reduced by
*ping*
On Tuesday, January 28, 2020 4:45:59 PM PST Andrew Benson wrote:
> I opened PR93486 for this problem:
>
> The following causes an ICE with revision
> ad690d79cfbb905c5546c9333c5fd089d906505b:
>
> module ivs
> interface l
> module procedure l_
> end interface l
> contains
> func
On Mon, Feb 10, 2020 at 02:24:15PM +0800, Kewen.Lin wrote:
> 2020-02-10 Kelvin Nilsen
> Kewen Lin
>
> * gcc.target/powerpc/p9-dform-0.c: New test.
> * gcc.target/powerpc/p9-dform-1.c: New test.
> * gcc.target/powerpc/p9-dform-2.c: New test.
> * gcc.target/p
Hi!
On Mon, Feb 10, 2020 at 02:20:17PM +0800, Kewen.Lin wrote:
> * tree-ssa-loop-manip.c (decide_uf_const_iter): New function.
> (decide_uf_runtime_iter): Likewise.
> (decide_uf_stupid): Likewise.
These names still use "uf". (Those are the last I see).
> * tree-ssa-loop-
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to master as r10-6568-geb031d4ba27b3fdc292f5a1092e66024f5ee239c.
gcc/analyzer/ChangeLog:
PR analyzer/93659
* analyzer.opt (-param=analyzer-max-recursion-depth=): Fix "tha"
-> "that" typo.
(Wanaly
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to master as r10-6567-ge87deb37649cfe480217fc83c8d56fe925600f93.
gcc/analyzer/ChangeLog:
PR analyzer/93350
* region-model.cc (region_model::get_lvalue_1):
Handle BIT_FIELD_REF.
(make_region_for_ty
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to master as r10-6566-ge953f9588d4a7ea4183d14914f915329cc37941f.
gcc/analyzer/ChangeLog:
PR analyzer/93647
* diagnostic-manager.cc
(diagnostic_manager::prune_for_sm_diagnostic): Bulletproof against
On Mon, 10 Feb 2020, Ulrich Weigand wrote:
> Given the above rule, in the last case __FINITE_MATH_ONLY__ should
> also be 0, right?
Yes.
> I'm not sure how this can be implemented in the current option handling
> framework. The -ffast-math handling case would have to check whether
> or not ther
cpplib-10.1-b20200209.pt_BR.po.gz
Description: Binary data
The Translation Project robot, in the
name of your translation coordinator.
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'cpplib' has been submitted
by the Brazilian Portuguese team of translators. The file is available at:
https://translationproject.org/latest/cpplib/pt_BR.po
(This file, 'cpp
On Sat, 8 Feb 2020, Sandra Loosemore wrote:
> > > BTW, I did run autoconf in every subdirectory that contains a
> > > configure.ac,
> > > but it appears only libstc++-v3 actually uses this test; all the other
> > > regenerated configure scripts were unchanged.
> >
> > There's some problem with th
The reporter of RHBZ #1798636 was mislead and confused by GCC
issuing -Wstringop-truncation for a possible overflow in strncat.
It took a few iterations to appreciate this subtlety and realize
the warning was of the wrong kind.
The attached patch adjusts the logic of the function responsible
for
Hi,
This adds a target_supports entry to check that the
_ieee128 keyword is understood by the target.
Also adds that require-effective-target check to the
existing pr92796 testcase.
Sniff tested on Linux (power6,power9) and AIX.
OK for master?
Thanks
-Will
[testsuite]
*
Hi,
This fixes up a few tests that explicitly disable vsx,
but still require altivec be enabled by adding the -maltivec
option. (Noted on AIX, also seen on Linux/Power6).
OK for master?
Thanks,
-Will
[testsuite]
* gcc.target/powerpc/pr70010-2.c: Add -maltivec.
* gc
Hi!
On Mon, Feb 10, 2020 at 02:17:04PM +0800, Kewen.Lin wrote:
> on 2020/1/20 下午8:33, Segher Boessenkool wrote:
> > On Thu, Jan 16, 2020 at 05:36:52PM +0800, Kewen.Lin wrote:
> >> As we discussed in the thread
> >> https://gcc.gnu.org/ml/gcc-patches/2020-01/msg00196.html
> >> Original: https://gcc
Alan recently changed the diagnostic in binutils for changing various
attributes of a section from a warning to a hard error.
This caused the FRV port to fail to build frvbegin/frvend because of
differences in the flags for the .ctors/.dtors sections.
This patch twiddles frvbegin.c/frvend.c in l
On Mon, Feb 10, 2020 at 03:52:13PM -0500, David Malcolm wrote:
> On Sun, 2020-02-09 at 16:38 -0800, Steve Kargl wrote:
> >
> > Having now looked at the patch, I think it's okay to commit.
> > As you note, it is new functionality in 10 so technically
> > cannot be a regression. But, it does fix a
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'cpplib' has been submitted
by the German team of translators. The file is available at:
https://translationproject.org/latest/cpplib/de.po
(This file, 'cpplib-10.1-b2020020
cpplib-10.1-b20200209.de.po.gz
Description: Binary data
The Translation Project robot, in the
name of your translation coordinator.
On Sun, 2020-02-09 at 16:38 -0800, Steve Kargl wrote:
> On Sun, Feb 09, 2020 at 04:19:13PM -0500, David Malcolm wrote:
> > On Sun, 2020-02-09 at 12:55 -0800, Steve Kargl wrote:
> > > On Sun, Feb 09, 2020 at 09:15:46PM +0100, Toon Moene wrote:
> > > > On 2/6/20 9:01 PM, David Malcolm wrote:
> > > >
On Mon, Feb 10, 2020 at 3:33 PM Jakub Jelinek wrote:
>
> Hi!
>
> As mentioned in the PR, for -mavx -mno-avx2 the backend does support
> vcondv4div4df and vcondv8siv8sf optabs (while generally 32-byte vectors
> aren't much supported in that case, it is performed using
> vandps/vandnps/vorps). The
On Mon, Feb 10, 2020 at 8:53 PM H.J. Lu wrote:
>
> On Mon, Feb 10, 2020 at 11:40 AM Uros Bizjak wrote:
> >
> > On Mon, Feb 10, 2020 at 8:22 PM H.J. Lu wrote:
> > >
> > > Since nested function isn't only called directly, there is ENDBR32 at
> > > function entry and we need to skip it for direct j
On Mon, Feb 10, 2020 at 11:40 AM Uros Bizjak wrote:
>
> On Mon, Feb 10, 2020 at 8:22 PM H.J. Lu wrote:
> >
> > Since nested function isn't only called directly, there is ENDBR32 at
> > function entry and we need to skip it for direct jump in trampoline.
>
> Hm, I'm afraid I don't understand this
On 2/10/20 8:21 PM, Patrick Palka wrote:
On Mon, 10 Feb 2020, Jason Merrill wrote:
On 2/10/20 2:20 PM, Patrick Palka wrote:
This patch fixes two issues with return type deduction in the presence of an
abbreviated function template.
The first issue (PR 69448) is that if a placeholder auto retu
On Mon, Feb 10, 2020 at 8:22 PM H.J. Lu wrote:
>
> Since nested function isn't only called directly, there is ENDBR32 at
> function entry and we need to skip it for direct jump in trampoline.
Hm, I'm afraid I don't understand this comment. Can you perhaps rephrase it?
Uros.
> Tested on Linux/x8
Hi
As show in the PR, The length used for the comparison for 'CFStringRef’ was
only comparing for 'CFString', potentially allowing mismatched identifiers.
fixed thus,
tested on x86_64-darwin16,
applied to master
thanks
Iain
Darwin: -Wformat-diag fix (PR93641)
The length used for the compa
Hello, gentle maintainer.
This is a message from the Translation Project robot. (If you have
any questions, send them to .)
A new POT file for textual domain 'gcc' has been made available
to the language teams for translation. It is archived as:
https://translationproject.org/POT-files/gcc
Since nested function isn't only called directly, there is ENDBR32 at
function entry and we need to skip it for direct jump in trampoline.
Tested on Linux/x86-64 CET machine with and without -m32.
gcc/
PR target/93656
* config/i386/i386.c (ix86_trampoline_init): Skip ENDBR32 at
On Mon, 10 Feb 2020, Jason Merrill wrote:
> On 2/10/20 2:20 PM, Patrick Palka wrote:
> > This patch fixes two issues with return type deduction in the presence of an
> > abbreviated function template.
> >
> > The first issue (PR 69448) is that if a placeholder auto return type
> > contains
> > an
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'cpplib' has been submitted
by the Ukrainian team of translators. The file is available at:
https://translationproject.org/latest/cpplib/uk.po
(This file, 'cpplib-10.1-b2020
cpplib-10.1-b20200209.uk.po.gz
Description: Binary data
The Translation Project robot, in the
name of your translation coordinator.
Hello, gentle maintainer.
This is a message from the Translation Project robot. (If you have
any questions, send them to .)
A new POT file for textual domain 'cpplib' has been made available
to the language teams for translation. It is archived as:
https://translationproject.org/POT-files/
Thanks - that worked.
On Monday, February 10, 2020 12:18:57 PM PST Segher Boessenkool wrote:
> On Mon, Feb 10, 2020 at 10:05:48AM -0800, Andrew Benson wrote:
> > I don't think I have the ability to mark the PR as resolved. Can someone
> > do
> > that?
>
> You have an @gcc.gnu.org account; if you
This patch renames the PowerPC internal switch -mprefixed-addr to be
-mprefixed.
Last week, Bill, Segher, and I were talking, and we came to the conclusion that
we needed to make the prefixed addressing option more public. This is
particularly true, when you consider that only 64-bit little endia
On 2/10/20 2:20 PM, Patrick Palka wrote:
This patch fixes two issues with return type deduction in the presence of an
abbreviated function template.
The first issue (PR 69448) is that if a placeholder auto return type contains
any modifiers such as & or *, then the abbreviated-function-template
On Mon, Feb 10, 2020 at 10:05:48AM -0800, Andrew Benson wrote:
> I don't think I have the ability to mark the PR as resolved. Can someone do
> that?
You have an @gcc.gnu.org account; if you use that for your BZ account,
you will magically get everything you need here.
Segher
On 2/10/20 5:28 PM, Patrick Palka wrote:
This patch improves the pretty printing of standard concept definitions in error
messages. In particular, standard concepts are now printed qualified whenever
appropriate, and the "concept" specifier is printed only when the
TFF_DECL_SPECIFIERS flag is sp
On Mon, Feb 10, 2020 at 12:00:28PM -0600, Segher Boessenkool wrote:
> On Mon, Feb 10, 2020 at 03:07:49PM +0100, Jakub Jelinek wrote:
> > + || strncmp (name, ".lbss.", sizeof (".lbss.") - 1) == 0
>
> You can just use strlen (".lbss.") which is nicer to read and compiles
> to the same thing?
I don't think I have the ability to mark the PR as resolved. Can someone do
that?
On Monday, February 10, 2020 10:02:24 AM PST Andrew Benson wrote:
> This is now committed (after adding the macro as Steve suggested):
>
> https://gcc.gnu.org/g:7848054c68bad6e2aa40cb59f77cc99bd8448d52
>
> On Sund
This is now committed (after adding the macro as Steve suggested):
https://gcc.gnu.org/g:7848054c68bad6e2aa40cb59f77cc99bd8448d52
On Sunday, February 9, 2020 4:32:26 PM PST Steve Kargl wrote:
> Patch looks to me. OK to commit.
>
> I'm wondering if we need a macro or helper function to
> simplif
On Mon, Feb 10, 2020 at 03:07:49PM +0100, Jakub Jelinek wrote:
> + || strncmp (name, ".lbss.", sizeof (".lbss.") - 1) == 0
You can just use strlen (".lbss.") which is nicer to read and compiles
to the same thing?
Segher
On Mon, Feb 10, 2020 at 10:20:50AM -0700, Martin Sebor wrote:
> PR 93641 points out a number of off-by-one mistakes in calls to strncmp
> in GCC where the bound is (unintentionally) less than the length of
> the string literal argument.
>
> PR 93640 is a separate report of another such mistake in
PR 93641 points out a number of off-by-one mistakes in calls to strncmp
in GCC where the bound is (unintentionally) less than the length of
the string literal argument.
PR 93640 is a separate report of another such mistake in the code that
validates the mode argument in attribute access. As a re
Random spotting. Exposes the missed benefit for delay-slot
filling of a splitter for indexed addressing mode (the [rN+M]
one). To be considered for common instructions and perhaps only
for suitable M; at least +-63 is obious (when there's a register
available) as both the original and the add fit
PR target/93372
* gcc.target/cris/pr93372-3.c, gcc.target/cris/pr93372-4.c,
gcc.target/cris/pr93372-6.c, gcc.target/cris/pr93372-7.c,
gcc.target/cris/pr93372-9.c, gcc.target/cris/pr93372-10.c,
gcc.target/cris/pr93372-11.c, gcc.target/cris/pr93372-12.c,
gcc.target/cris/pr93372-13.c, gcc.target/cris/
* gcc.target/cris/pr93372-2.c, gcc.target/cris/pr93372-5.c,
gcc.target/cris/pr93372-8.c: New tests.
These tests fails miserably both at being an example of cc0
eliminating compare instructions, and post-cc0-CRIS at showing a
significant improvement. They're here to track suboptimal
comparison cod
This test was separated from the posted and approved patch named
"dbr: Filter-out TARGET_FLAGS_REGNUM from end_of_function_needs"
and applied: it doesn't fail yet. It differs from the posted
version in that function "g" is commented-out; see the added
comment.
---
gcc/testsuite/gcc.target/cris/pr
To simplify separating the cc0-specific xfails, let's have an
effective-target.
This likely fits all targets.
---
gcc/testsuite/gcc.target/cris/cris.exp | 11 +++
1 file changed, 11 insertions(+)
diff --git a/gcc/testsuite/gcc.target/cris/cris.exp
b/gcc/testsuite/gcc.target/cris/cris.ex
* config/cris/cris.c (cris_reduce_compare): New function.
* config/cris/cris-protos.h (cris_reduce_compare): Add prototype.
* config/cris/cris.md ("cbranch4", "cbranchdi4", "cstoredi4")
(cstore4"): Apply cris_reduce_compare in expanders.
The decc0ration work of the CRIS port made me look closer a
Stuff I broke out from the CRIS decc0ration work;
compare-decanonicalization and tests that would be regressions
in a future timeline, but fixed later on.
Besides the first patch, nothing you'd normally care about, and
perhaps for people doing CC0 work: the test-cases and the cc0
effective-target
On 10/02/2020 09:27, Christophe Lyon wrote:
On Fri, 7 Feb 2020 at 17:55, Richard Earnshaw (lists)
wrote:
On 07/02/2020 16:43, Christophe Lyon wrote:
On Fri, 7 Feb 2020 at 14:49, Richard Earnshaw (lists)
wrote:
On 07/02/2020 13:19, Christophe Lyon wrote:
When running the testsuite with -fd
This patch improves the pretty printing of standard concept definitions in error
messages. In particular, standard concepts are now printed qualified whenever
appropriate, and the "concept" specifier is printed only when the
TFF_DECL_SPECIFIERS flag is specified.
In the below test, the first erro
Segher Boessenkool wrote:
> On Fri, Feb 07, 2020 at 05:47:32PM +0100, Ulrich Weigand wrote:
> > > but what happens to -fsignalling-nans -ffast-math then? Better leave
> > > those
> > > in I'd say.
> >
> > Ah, it seems I was confused about the intended semantics here.
> >
> > I thought that a *m
Joseph Myers wrote:
> On Fri, 7 Feb 2020, Ulrich Weigand wrote:
>
> > I thought that a *more specific* option like -fsignalling-nans was always
> > intended to override a more generic option like -ffast-math, no matter
> > whether it comes before or after it on the command line.
>
> Yes, that's c
ChangeLog:
PR target/91489
* config/i386/i386.md (simple_return): Also check
for ms_hook_prologue function attribute.
* config/i386/i386.c (ix86_can_use_return_insn_p):
Also check for ms_hook_prologue function attribute.
testsuite/ChangeLog:
PR target/91489
* gc
The peephole that detects a mov of one register to another followed by
a comparison of the original register against zero is only used in Arm
state; but the instruction that matches this is generic to all 32-bit
compilation states. That instruction lacks support for SP which is
permitted in Arm s
On 01/02/2020 08:30, Jakub Jelinek wrote:
Hi!
The following testcase ICEs on arm. The problem is that the following
peephole tries to match adjacent *arm_movsi_insn + *arm_cmpsi_insn;
the *arm_movsi_insn uses =rk, rk constraints and *arm_cmpsi_insn
uses r, IL constraints for what is matched by
Committed as obvious.
gcc:
* md.texi (Define Subst): Match closing paren in example.
diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi
index cec74ea78..66c5eea3b 100644
--- a/gcc/doc/md.texi
+++ b/gcc/doc/md.texi
@@ -10545,7 +10545,7 @@ generated with the following @code{define_subst}:
""
On Mon, 10 Feb 2020, Jonathan Wakely wrote:
> On 07/02/20 13:59 -0500, Patrick Palka wrote:
> > Since basic_istream_view::iterator is neither a cpp17 iterator (because it's
> > move-only) nor does it define all four of the types {difference_type,
> > value_type, reference, iterator_category}, then
On Mon, Feb 10, 2020 at 03:40:18PM +0100, Richard Biener wrote:
> Hmm. Maybe with FP operands we can also try to implement the mask
> as != 0.0 FP condition? Not sure if -1 (or 1) is enough non-NaNish to
> not cause problems of course.
Well, by the time we reach expansion, we have just the VECTO
On Mon, Feb 10, 2020 at 3:33 PM Jakub Jelinek wrote:
>
> Hi!
>
> As mentioned in the PR, for -mavx -mno-avx2 the backend does support
> vcondv4div4df and vcondv8siv8sf optabs (while generally 32-byte vectors
> aren't much supported in that case, it is performed using
> vandps/vandnps/vorps). The
On Mon, 10 Feb 2020 at 14:53, Jason Merrill wrote:
>
> On Mon, Feb 10, 2020 at 2:13 PM Christophe Lyon
> wrote:
>>
>> On Fri, 7 Feb 2020 at 14:54, Jason Merrill wrote:
>> >
>> > Here we were swallowing all the syntax errors by parsing tentatively, and
>> > returning error_mark_node without ever
On Mon, Feb 10, 2020 at 03:25:43PM +0100, Jakub Jelinek wrote:
> Hi!
>
> The last argument to strncasecmp is incorrect, so it matched even when
> can%' wasn't followed by t. Also, the !ISALPHA (format_chars[1]) test
> looks pointless, format_chars[1] must be ' if strncasecmp succeeded and
> so wi
On Mon, 10 Feb 2020 at 14:26, Jakub Jelinek wrote:
>
> On Mon, Feb 10, 2020 at 02:03:47PM +0100, Christophe Lyon wrote:
> > > 2020-02-07 Jakub Jelinek
> > >
> > > PR target/93615
> > > * config/arm/unwind-arm.h (gnu_Unwind_Find_got): Rename to ...
> > > (_Unwind_gnu_Find
Hi!
As mentioned in the PR, for -mavx -mno-avx2 the backend does support
vcondv4div4df and vcondv8siv8sf optabs (while generally 32-byte vectors
aren't much supported in that case, it is performed using
vandps/vandnps/vorps). The problem is that after the last generic vector
lowering (where the V
Hi!
The last argument to strncasecmp is incorrect, so it matched even when
can%' wasn't followed by t. Also, the !ISALPHA (format_chars[1]) test
looks pointless, format_chars[1] must be ' if strncasecmp succeeded and
so will never be ISALPHA.
Fixed thusly, bootstrapped/regtested on x86_64-linux
Hi!
I'm not aware of symbols starting with _ZG that don't start with _ZGR
prefix, but perhaps in the future there might be some.
Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux,
committed to trunk as obvious.
2020-02-10 Jakub Jelinek
PR other/93641
* error
Hi!
Clearly I can't count, so we would consider as SECTION_BSS even sections
like .lbssfoo or .gnu.linkonce.lbbar, even when linker only considers as
special .lbss or .lbss.baz or .gnu.linkonce.lb.qux.
Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux,
committed to trunk as obvi
On Mon, Feb 10, 2020 at 2:13 PM Christophe Lyon
wrote:
> On Fri, 7 Feb 2020 at 14:54, Jason Merrill wrote:
> >
> > Here we were swallowing all the syntax errors by parsing tentatively, and
> > returning error_mark_node without ever actually giving an error. Fixed
> by
> > using save_tokens/roll
Hi Andrew,
On Sat, 8 Feb 2020 at 10:16, Andrew Pinski wrote:
>
> Hi,
> These two patches are what I use to fix testing of the santizers
> with qemu. The first one disables coloring always as for some reason
> when running with qemu (but not normally), coloring is detected. I
> have not gone
On 2/3/20 11:20 AM, Stam Markianos-Wright wrote:
On 1/27/20 3:54 PM, Stam Markianos-Wright wrote:
On 1/16/20 4:05 PM, Stam Markianos-Wright wrote:
On 1/10/20 6:48 PM, Stam Markianos-Wright wrote:
On 12/18/19 1:25 PM, Stam Markianos-Wright wrote:
On 12/13/19 10:22 AM, Stam Markianos
On Mon, Feb 10, 2020 at 5:33 AM Mihailo Stojanovic
wrote:
>
> Similar to the mirror case of allocating an FPR for an integer mode
> pseudo, prevent GPRs from being allocated for a floating mode pseudo.
Can you expand on why you want to do this?
Provide benchmarking or a testcase which this improv
Similar to the mirror case of allocating an FPR for an integer mode
pseudo, prevent GPRs from being allocated for a floating mode pseudo.
gcc/ChangeLog:
* gcc/config/mips/mips.c (mips_ira_change_pseudo_allocno_class):
Limit the allocation of floating mode pseudos to FP_REGS.
---
Please disregard this.
Forgot to add the ChangeLog entry.
Mihailo
On Mon, Feb 10, 2020 at 02:03:47PM +0100, Christophe Lyon wrote:
> > 2020-02-07 Jakub Jelinek
> >
> > PR target/93615
> > * config/arm/unwind-arm.h (gnu_Unwind_Find_got): Rename to ...
> > (_Unwind_gnu_Find_got): ... this. Use __asm instead of asm. Remove
> > tr
This patch fixes two issues with return type deduction in the presence of an
abbreviated function template.
The first issue (PR 69448) is that if a placeholder auto return type contains
any modifiers such as & or *, then the abbreviated-function-template
compensation in splice_late_return_type doe
On Fri, 7 Feb 2020 at 14:54, Jason Merrill wrote:
>
> Here we were swallowing all the syntax errors by parsing tentatively, and
> returning error_mark_node without ever actually giving an error. Fixed by
> using save_tokens/rollback_tokens instead.
>
> Tested x86_64-pc-linux-gnu, applying to trun
Hi,
On Fri, 7 Feb 2020 at 09:19, Jakub Jelinek wrote:
>
> Hi!
>
> As the following testcase shows, unwind.h on ARM can't be (starting with GCC
> 10) compiled with -std=c* modes, only -std=gnu* modes.
> The problem is it uses asm keyword, which isn't a keyword in those modes
> (system headers vs.
Hi Bin,
Bin.Cheng wrote:
> Ping.
We are seeking to clarify the standard wording around this (and the cases where
unhandled_exception() returns - hopefully during the WG21 meeting this week,
FWIW, I think your interpretation makes sense here.
thanks
Iain
>
> Thanks,
> bin
>
> On Mon, Feb 3,
1 - 100 of 110 matches
Mail list logo
