gcc define __FLT_EVAL_METHOD__ according to
builtin_define_with_int_value ("__FLT_EVAL_METHOD__",
c_flt_eval_method (true));
and guess we need to handle things like:
/* GCC only supports one interchange type right now, _Float16. If
we're evaluating _Float16 in 16-bit precision, then
> I’m not sure what the fix should be, either. We could use fixinclude to make
> the darwin headers happy, but we don’t really have a macro to provide the
> right value. Like a __FLT_EVAL_METHOD_OLDSTYLE__ macro.
>
> What should be the float_t and double_t types for FLT_EVAL_METHOD == 16?
> flo
Hi,
> See https://gcc.gnu.org/bugzilla//show_bug.cgi?id=100854 .
I found that, indeed, but what I struggle to see is: this behaviour of
__FLT_EVAL_METHOD__ has been around for several years now, so why aren’t there
more tests failing?
I’m not sure what the fix should be, either. We could use
Snapshot gcc-9-20211223 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/9-20211223/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 9 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Thu, Dec 23, 2021, 14:24 FX via Gcc wrote:
> Hi,
>
> Some recently introduced tests have been failing for several weeks on
> x86_64-apple-darwin.
>
> FAIL: gcc.target/i386/cond_op_maxmin__Float16-1.c
> FAIL: gcc.target/i386/pr102464-copysign-1.c
> FAIL: gcc.target/i386/pr102464-fma.c
> FAIL: g
Hi,
Some recently introduced tests have been failing for several weeks on
x86_64-apple-darwin.
FAIL: gcc.target/i386/cond_op_maxmin__Float16-1.c
FAIL: gcc.target/i386/pr102464-copysign-1.c
FAIL: gcc.target/i386/pr102464-fma.c
FAIL: gcc.target/i386/pr102464-maxmin.c
FAIL: gcc.target/i386/pr102464
Hi David, hi everone,
I’m trying to understand how best to fix or silence the several failures in
gcc.dg/analyzer that occur on x86_64-apple-darwin. Some of them, according to
gcc-testresults, also occur on other non-Linux targets. See for example, the
test results at
https://gcc.gnu.org/piper
On Thu, 23 Dec 2021 at 13:10, Martin Liška wrote:
> >> On 11/22/21 20:01, Dmitry Vyukov wrote:
> >>> I've already reverted the change. So I will include a fix into the next
> >>> version.
> >>> Thanks for notifying.
> >>
> >> Hello.
> >>
> >> Am I correct that the patch set is installed again? An
On 11/30/21 05:17, Dmitry Vyukov wrote:
On Mon, 29 Nov 2021 at 19:16, Martin Liška wrote:
On 11/22/21 20:01, Dmitry Vyukov wrote:
I've already reverted the change. So I will include a fix into the next version.
Thanks for notifying.
Hello.
Am I correct that the patch set is installed again
On Thu, 23 Dec 2021, 06:07 Alessandro Baretta via Gcc,
wrote:
>
> How I might help diagnose and fix this bug? For instance, how does one
> run gcc from inside gdb? I know that gcc is just the driver and
> cc1plus is the actual compiler, so I presume I'd have to run cc1plus
> inside gdb, but as fa
10 matches
Mail list logo
