On 08/22/2016 03:40 PM, Jonathan Wakely wrote:
> What's going on?!
>
> Have I fundamentally misunderstood something about how RUNTESTFLAGS or
> effective-target keywords work?
>
Here's a wild guess.
In gdb's testsuite, I've seen odd problems like these being caused by some
tcl global getting s
The GNU Compiler Collection version 6.2 has been released.
GCC 6.2 is a bug-fix release from the GCC 6 branch
containing important fixes for regressions and serious bugs in
GCC 6.1 with more than 110 bugs fixed since the previous release.
This release is available from the FTP servers listed at:
On 08/21/2016 05:59 PM, Segher Boessenkool wrote:
On Sun, Aug 21, 2016 at 02:04:49PM -0500, Daniel Santos wrote:
Thanks for the response! Perhaps an UNSPEC insn is needed here because I
have work to do on other passes too. For example, when the debug info is
created, it's giving the wrong locati
I'm confused by what I'm seeing when running the libstdc++ tests with:
RUNTESTFLAGS='--target_board=\"unix{-std=gnu++98,-std=gnu++11,-std=gnu++14,-std=gnu++17}\"'
If I inspect the libstdc++.sum file to look for the results for a
particular file that has { dg-do compile { target c++14 } }, I find
Hi,
While implementing divmod transform:
https://gcc.gnu.org/ml/gcc-patches/2016-05/msg01757.html
I ran into an issue with optab_libfunc().
It appears optab_libfunc (sdivmod_optab, DImode) returns
a libfunc with name "__divmoddi4", even though such a libfunc
does not exist in libgcc. This happens
Status
==
GCC 6.2 has been released, the GCC 6 branch is now open
for regression and documentation fixes again.
Quality Data
Priority # Change from last report
--- ---
P10
P2 124 - 3
P3
