I'll make a fool of myself but I still have further questions if you don't
mind (see inline).
On Friday, 4 May 2018, Segher Boessenkool
wrote:
> Hi!
>
> On Wed, May 02, 2018 at 07:57:55AM +0100, Thomas Preudhomme wrote:
>> As mentionned in the ticket this was my first
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81091
Jc Yang changed:
What|Removed |Added
CC||bandinfinite at gmail dot com
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85645
Bug ID: 85645
Summary: ICE in maybe_record_trace_start, at dwarf2cfi.c:2348
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: ice-checking, ice-on-invalid-code
Update mkalldocs.sh from the current master sources, replacing the old
mkdoc.sh. I think this got left out of the merges. Bootstrapped and
ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
Since libgo does have the vet tool now, enable the tests in which the
go tool invokes it. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
===
---
In https://golang.org/cl/111097 the gc version of cmd/go, which is
part of libgo, was updated to include some gccgo-specific changes. The
libgo code already has different versions of those changes; this patch
makes the libgo match the upstream code. Bootstrapped and ran Go
testsuite on
--prefix=/Users/urabe.shyouhei/target --program-suffix=-trunk
--enable-languages=c --disable-bootstrap
--cache-file=/Users/urabe.shyouhei/data/build/gcc/config.cache
Thread model: posix
gcc version 9.0.0 20180503 (experimental) (GCC)
COLLECT_GCC_OPTIONS='-v' '-fstack-protector' '-mmacosx-version
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85643
Bug ID: 85643
Summary: attribute nonstring fails to squash
-Wstringop-truncation warning
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78063
Romain Geissler changed:
What|Removed |Added
CC||romain.geissler at amadeus dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85641
--- Comment #2 from Steve Kargl ---
On Thu, May 03, 2018 at 11:12:26PM +, kargl at gcc dot gnu.org wrote:
>
> #31 0x008ad88d in gfc_code_walker (c=0x2ca231808,
> codefn=codefn@entry=0x8a90d0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85600
--- Comment #9 from Jason Merrill ---
Author: jason
Date: Thu May 3 23:35:20 2018
New Revision: 259913
URL: https://gcc.gnu.org/viewcvs?rev=259913=gcc=rev
Log:
PR c++/85600 - virtual delete failure.
* init.c (build_delete):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85600
Jason Merrill changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
When I removed some of the save_exprs, I was missing that we don't
save_expr on the virtual delete path, but then we use addr again to
check that it's non-null.
This patch simplifies the logic a bit so that we always save_expr when
we're deleting; if we're just calling the destructor we don't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83476
Guillaume Racicot changed:
What|Removed |Added
Keywords||rejects-valid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85641
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61502
James Y Knight changed:
What|Removed |Added
CC||foom at fuhm dot net
--- Comment #24
Following a recent change for PR 82644 the non-standard hypergeomtric
functions are not defined by when __STRICT_ANSI__ is defined
(e.g. for -std=c++17, or -std=c++14 -D__STDCPP_WANT_MATH_SPEC_FUNCS__).
That caused errors in because the using-declarations for
tr1::hyperg et al are invalid in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82644
--- Comment #6 from Jonathan Wakely ---
Author: redi
Date: Thu May 3 22:58:43 2018
New Revision: 259912
URL: https://gcc.gnu.org/viewcvs?rev=259912=gcc=rev
Log:
PR libstdc++/82644 define TR1 hypergeometric functions in strict modes
Following
Snapshot gcc-7-20180503 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20180503/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85642
Bug ID: 85642
Summary: Wrong implicit exception-specification with
std::optional
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85641
Bug ID: 85641
Summary: [7/8 Regression] ICE with string concatenate
Product: gcc
Version: 7.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
Hi Than,
> Thanks for catching that.
>
> I don't have access to test machines, but could you possibly try the
> attached patch?
I just did. However, it made no difference, while a full reversal of
the patch fixed all new go and libgo failures on sparc-sun-solaris2.11.
Rainer
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55307
--- Comment #6 from H.J. Lu ---
Dup.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85100
H.J. Lu changed:
What|Removed |Added
CC||luto at kernel dot org
--- Comment #13 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55307
H.J. Lu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85637
--- Comment #2 from petschy at gmail dot com ---
Thanks. For non-char types, one can use __restrict on ptrs, but for chars it
doesn't work, unfortunately (strict aliasing rules). Is there a way to tell the
compiler that a char ptr doesn't alias
On Thu, May 3, 2018 at 12:29 AM, Richard Biener
wrote:
> Just as a note, IIRC all the SUBREG_PROMOTED_* stuff is quite fragile
> - I remember
> Eric fixing things up a bit but some verification would be nice to
> have (instrumentation
> at RTL level that for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85640
Bug ID: 85640
Summary: Code size regression vs 7.3.1
Product: gcc
Version: 8.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85639
Bug ID: 85639
Summary: ICE in compiling new test cases added in r259850
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80947
--- Comment #17 from Duarte ---
It also fails on GCC 8.1. This is the reproducer:
template
void foo() {
struct inner {
inner() {
([this] { });
}
};
}
int main() { foo(); }
It fails when compiled with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85600
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85632
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85632
--- Comment #4 from Jonathan Wakely ---
Author: redi
Date: Thu May 3 20:39:31 2018
New Revision: 259911
URL: https://gcc.gnu.org/viewcvs?rev=259911=gcc=rev
Log:
PR libstdc++/85632 fix wraparound in filesystem::space
On 32-bit targets any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55307
Nathaniel J. Smith changed:
What|Removed |Added
CC||njs at pobox dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84769
--- Comment #13 from Duarte ---
Awesome, thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85638
--- Comment #2 from xantares09 at hotmail dot com ---
Created attachment 44061
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44061=edit
./src/gcc-build-i686-w64-mingw32/gcc/ada/rts/a-calend.adb
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85638
--- Comment #1 from xantares09 at hotmail dot com ---
Created attachment 44060
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44060=edit
??
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85638
Bug ID: 85638
Summary: gcc 8.1.0 fails to build ada language for target
i686-w64-mingw32
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84769
Jonathan Wakely changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84769
--- Comment #11 from Jonathan Wakely ---
Author: redi
Date: Thu May 3 20:16:34 2018
New Revision: 259910
URL: https://gcc.gnu.org/viewcvs?rev=259910=gcc=rev
Log:
PR libstdc++/84769 qualify call to std::get<0>
PR libstdc++/84769
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85632
--- Comment #3 from Jonathan Wakely ---
Author: redi
Date: Thu May 3 20:16:29 2018
New Revision: 259909
URL: https://gcc.gnu.org/viewcvs?rev=259909=gcc=rev
Log:
PR libstdc++/85632 fix wraparound in filesystem::space
On 32-bit targets any
Hi,
this is basically the same patch I posted a few months ago,
with a few formatting nits by Jakub fixed.
Bootstrapped and reg-tested again with current trunk.
Is it OK for trunk?
Bernd.
On 12/15/17 11:44, Bernd Edlinger wrote:
> Hi,
>
> when working on the -Wcast-function-type patch I
On 02/05/2018 13:49, Jonathan Wakely wrote:
On 01/05/18 21:56 +0200, François Dumont wrote:
Hi
If not told otherwise I'll commit attached patch tomorrow.
Please do not commit it, see below.
Already discussed here:
https://gcc.gnu.org/ml/libstdc++/2017-10/msg00053.html
There's no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85637
--- Comment #1 from Andrew Pinski ---
This is most likely because unsigned char is considered as aliasing any type.
That means the write to this->m_s1 and this->m_s2 can be read via *buf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85637
Bug ID: 85637
Summary: Unneeded store of member variables in inner loop
Product: gcc
Version: 7.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84769
--- Comment #10 from Jonathan Wakely ---
Author: redi
Date: Thu May 3 19:53:46 2018
New Revision: 259907
URL: https://gcc.gnu.org/viewcvs?rev=259907=gcc=rev
Log:
PR libstdc++/84769 qualify call to std::get<0>
PR libstdc++/84769
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85632
--- Comment #2 from Jonathan Wakely ---
Author: redi
Date: Thu May 3 19:53:42 2018
New Revision: 259906
URL: https://gcc.gnu.org/viewcvs?rev=259906=gcc=rev
Log:
PR libstdc++/85632 fix wraparound in filesystem::space
On 32-bit targets any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85636
Bug ID: 85636
Summary: Tree if-conversion inserts bogus loads
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
. Committed to mainline.
> I strongly suspect that this patch severely broke Go on Solaris/SPARC:
> between 20180502 (r259840) and 20180503 (r259897) there appeared tons of
> new execution failures, both 32 and 64-bit:
> +FAIL: go.go-torture/execute/printnil.go execution, -O0
> +F
As prophesied in GCC 8.1, it's time to kill friend injection.
Committing to trunk.
nathan
--
Nathan Sidwell
2018-05-03 Nathan Sidwell
* doc/extend.texi (Deprecated Features): Remove
-ffriend-injection.
(Backwards Compatibility): Likewise.
* doc/invoke.texi (C++ Language
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85530
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
and ran
> Go testsuite on x86_64-pc-linux-gnu. Committed to mainline.
I strongly suspect that this patch severely broke Go on Solaris/SPARC:
between 20180502 (r259840) and 20180503 (r259897) there appeared tons of
new execution failures, both 32 and 64-bit:
+FAIL: go.go-torture/execute/printn
On 03/05/18 20:55 +0200, Duarte Nunes wrote:
PR libstdc++/84769
* include/std/variant (visit<_Visitor, _Variants...>):
Qualify call to std::get<_Np, _Types...>.
Thanks for the patch, I was already testing the same change and just
committed the attached patch to trunk. Backports for other
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85530
--- Comment #2 from Jakub Jelinek ---
Author: jakub
Date: Thu May 3 18:59:39 2018
New Revision: 259903
URL: https://gcc.gnu.org/viewcvs?rev=259903=gcc=rev
Log:
PR target/85530
* config/i386/avx512fintrin.h (_mm512_mullox_epi64,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85632
--- Comment #1 from Jonathan Wakely ---
Author: redi
Date: Thu May 3 18:58:00 2018
New Revision: 259901
URL: https://gcc.gnu.org/viewcvs?rev=259901=gcc=rev
Log:
PR libstdc++/85632 fix wraparound in filesystem::space
On 32-bit targets any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84769
--- Comment #9 from Jonathan Wakely ---
Author: redi
Date: Thu May 3 18:58:04 2018
New Revision: 259902
URL: https://gcc.gnu.org/viewcvs?rev=259902=gcc=rev
Log:
PR libstdc++/84769 qualify call to std::get<0>
PR libstdc++/84769
On 32-bit targets any values over 4GB would wrap and produce the wrong
result.
PR libstdc++/85632 use uintmax_t for arithmetic
* src/filesystem/ops.cc (experimental::filesystem::space): Perform
arithmetic in result type.
* src/filesystem/std-ops.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84769
--- Comment #8 from Duarte ---
I tried to go ahead and send a patch for this (should be on the gcc-patches and
libstdc++ lists).
PR libstdc++/84769
* include/std/variant (visit<_Visitor, _Variants...>):
Qualify call to std::get<_Np, _Types...>.
Signed-off-by: Duarte Nunes
---
ChangeLog| 6 ++
libstdc++-v3/include/std/variant | 2 +-
2 files changed, 7 insertions(+), 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84769
Jonathan Wakely changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
> From: Nathan Sidwell [mailto:nathanmsidw...@gmail.com] On Behalf Of
> Nathan Sidwell
> Sent: Thursday, May 3, 2018 1:58 PM
> To: taylor, david; gcc@gcc.gnu.org
> Subject: Re: gcov and initialized data
>
> On 05/03/2018 01:09 PM, taylor, david wrote:
>
> > When you build your program for code
Consider the attached Fortran code (the most expensive routine,
computation-wise, in our weather forecasting model).
verint.s.7.3 is the result of:
gfortran -g -O3 -S -march=native -mtune=native verint.f
using release 7.3.
verint.s.8.1 is the result of:
gfortran -g -O3 -S -march=native
These patches were previously posted in March as RFC's. These patches just
reformat the floating point move insns to make it easier to figure out which
constraints and attributes are used for particular alternatives.
I have built the compiler on a little endian power8 system with all 5 patches
These patches were previously posted in March as RFC's. These patches just
reformat the floating point move insns to make it easier to figure out which
constraints and attributes are used for particular alternatives.
I have built the compiler on a little endian power8 system with all 5 patches
These patches were previously posted in March as RFC's. These patches just
reformat the floating point move insns to make it easier to figure out which
constraints and attributes are used for particular alternatives.
I have built the compiler on a little endian power8 system with all 5 patches
These patches were previously posted in March as RFC's. These patches just
reformat the floating point move insns to make it easier to figure out which
constraints and attributes are used for particular alternatives.
I have built the compiler on a little endian power8 system with all 5 patches
These patches were previously posted in March as RFC's. These patches just
reformat the floating point move insns to make it easier to figure out which
constraints and attributes are used for particular alternatives.
I have built the compiler on a little endian power8 system with all 5 patches
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85635
--- Comment #2 from John Marino ---
I would think every condition after (e.g. __APPLE__, __linux__, _AIX) would
fail as well. Wouldn't cpp abort on QNX before the __APPLE__ condition is
evaluated?
Hi Jakub,
> On 3 May 2018, at 12:28, Jakub Jelinek wrote:
>
> On Thu, Apr 26, 2018 at 10:09:48PM +0200, Jakub Jelinek wrote:
>> ICC apparently has these two intrinsics (why it doesn't have a maskz_ one
>> is unclear to me) which are like _mm512_{,mask_}mullo_epi64, except they
On 05/03/2018 01:09 PM, taylor, david wrote:
When you build your program for code coverage (-ftest-coverage -fprofile-arcs),
GCC creates some initialized read-write GCOV related data. Has anyone modified
GCC to, presumably either under control of a command line option or possibly a
configure
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85635
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85634
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85635
Bug ID: 85635
Summary: gcc8+: typo in link.c renders gnat unbuildable on
non-windows, non hpux
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899
--- Comment #8 from Antony Polukhin ---
(In reply to Richard Biener from comment #4)
> (In reply to Antony Polukhin from comment #2)
> > Looks like [class.ctor] paragraph 14 covers this case:
> >
> > "During the construction of an object, if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85634
--- Comment #4 from Andrew Paprocki ---
(In reply to Marek Polacek from comment #1)
> Please submit a full bug report, with preprocessed source if appropriate.
I had to attach the .ii and .s file tgz'd due to the file size limit of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85634
--- Comment #3 from Andrew Paprocki ---
Compiler info:
$ g++-8 -v
Reading specs from /dev/shm/refroot/opt/bb/lib/gcc-8.1/bin/../lib/gcc/specs
COLLECT_GCC=/dev/shm/refroot/opt/bb/bin/g++-8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85634
--- Comment #2 from Andrew Paprocki ---
Created attachment 44057
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44057=edit
-save-temps output
> Test coverage of -fnon-call-exceptions is notoriously bad and I'm not
> sure whether Ada uses GCCs complex types. Eric?
It does, but only with a GNAT-specific pragma:
https://gcc.gnu.org/onlinedocs/gcc-8.1.0/gnat_rm/Pragma-Complex_005fRepresentation.html#Pragma-Complex_005fRepresentation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84769
--- Comment #6 from Duarte ---
I think that calls to get<0> should be scoped, for example in visit().
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80947
Duarte changed:
What|Removed |Added
CC||duarte at scylladb dot com
--- Comment #16
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85633
--- Comment #4 from Julian Taylor ---
Oh that is unfortunate.
I guess one has to inject the dependency in the fpu checking function as an
argument then.
These patches were previously posted in March as a RFC, and I would like to
check them into the trunk. These patches make the mode_supports* functions use
similar names for the functions that return if a mode supports D-FORM, DS-FORM,
and/or DQ-FORM instructions, and add the ability to ask
These patches were previously posted in March as a RFC, and I would like to
check them into the trunk. These patches make the mode_supports* functions use
similar names for the functions that return if a mode supports D-FORM, DS-FORM,
and/or DQ-FORM instructions, and add the ability to ask
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85634
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
This patch to the Go frontend by Than McIntosh tweaks the array type
checking code to avoid crashing on array types whose length
expressions are explicit non-integer types (for example,
"float64(10)"). If such constructs are seen, issue an "invalid array
bound" error. This fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85634
Bug ID: 85634
Summary: 8.1 ICE in tsubst_copy, at cp/pt.c:15483
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
These patches were previously posted in March as a RFC, and I would like to
check them into the trunk. These patches make the mode_supports* functions use
similar names for the functions that return if a mode supports D-FORM, DS-FORM,
and/or DQ-FORM instructions, and add the ability to ask
These patches were previously posted in March as a RFC, and I would like to
check them into the trunk. These patches make the mode_supports* functions use
similar names for the functions that return if a mode supports D-FORM, DS-FORM,
and/or DQ-FORM instructions, and add the ability to ask
--resend Michael's reply
On Mon, Apr 30, 2018 at 1:19 PM, Michael Eager wrote:
>
> Applied -- Committed revision 259758.
>
> Andrew -- Please re-run GCC regression test to verify that nothing
> was lost in the editing.
>
>
>
> --
> Michael Eagerea...@eagerm.com
> 1960 Park
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85628
--- Comment #1 from Andrew Pinski ---
>This should just be a matter of adding the necessary patterns in aarch64.md.
I was doing for MIPS and it was rejected because combine or something before
combine should be generating zero_extract on the
I want to use gcov in an embedded type environment. It supports both cold boot
and warm boot.
For warm boot it does not reload the program from media, instead it 'just' jumps
to the start and begins again. Due to support for warm boot, it does not
support
read-write initialized data. Writable
Hi!
OpenMP 5.0 will extend the defaultmap clause from always just the
default(tofrom:scalar) form to have various default behaviors before the
: and various categories after the : (plus no : category to cover all
categories).
There are some issues I've raised on omp-lang, this patch implements
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85633
--- Comment #3 from Andrew Pinski ---
See PR 38960 for why I said this is not a regression.
On 05/03/2018 10:55 AM, Segher Boessenkool wrote:
> Hi!
>
> On Wed, May 02, 2018 at 07:57:55AM +0100, Thomas Preudhomme wrote:
>> As mentionned in the ticket this was my first thought but this means
>> making the pattern aware of all the possible way the address could be
>> access (PIC Vs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67650
--- Comment #30 from Vincent ---
Am using OSX, but I do not believe it makes a big difference. Thanks, Jonathan,
let me know if I can help in any way.
(In reply to Jonathan Wakely from comment #29)
> (In reply to Vincent from comment #27)
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85633
--- Comment #2 from Julian Taylor ---
changing the fpu state does not count as a side effect?
This doesn't seem plausible, this type of code is one the reasons the fpu
exception state exists.
There is a lot of code written with this in mind
On 03/05/18 12:59 +0100, Jonathan Wakely wrote:
Also define __remove_cvref_t for internal use before C++2a.
* include/std/any (any_cast): Use __remove_cvref_t.
* include/std/tuple (__make_tuple): Likewise.
* include/std/type_traits (__remove_cvref_t): Define.
Hi!
On Wed, May 02, 2018 at 07:57:55AM +0100, Thomas Preudhomme wrote:
> As mentionned in the ticket this was my first thought but this means
> making the pattern aware of all the possible way the address could be
> access (PIC Vs non-PIC, Arm Vs Thumb-2 Vs Thumb-1) to decide how many
> scratch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85633
Andrew Pinski changed:
What|Removed |Added
Component|c |middle-end
Summary|[8
On Thu, May 03, 2018 at 06:35:50PM +0200, Jakub Jelinek wrote:
> That requires a machine_mode or tree, but I don't have either of those,
> nor the caller (fold_const_call_sss) has those.
>
> I could change it to:
> if (flag_signalling_nans
> && !flag_finite_math_only
> &&
1 - 100 of 217 matches
Mail list logo