https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80432
Hao Zhang changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80717
--- Comment #2 from Hao Zhang ---
Thank you for your reply. For me basically any arguments with /usr/bin/gcc-ar
fails with segfault, even running /usr/bin/gcc-ar with no additional arguments
at all.
When I run gcc-ar with gdb (here I don't even
: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: theivorytower at gmail dot com
Target Milestone: ---
When I run any of the LTO wrappers (gcc-ar, gcc-nm, gcc-ranlib) with absolute
path (e.g. /usr/bin/gcc-ar), the program segfaults immediately. I tried to run
some
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80432
--- Comment #3 from Hao Zhang ---
(In reply to Hao Zhang from comment #2)
> (In reply to Martin Liška from comment #1)
> > Can't reproduce, can you please provide options you use to build the
> > executable?
>
> I didn't use any extra options be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80432
--- Comment #2 from Hao Zhang ---
(In reply to Martin Liška from comment #1)
> Can't reproduce, can you please provide options you use to build the
> executable?
I didn't use any extra options besides g++ pow.cpp, and both my CFLAGS and
CXXFLAGS
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: theivorytower at gmail dot com
Target Milestone: ---
With the latest gcc 7.0.1, whenever I pass long double arguments to std::pow,
the results are either nan or inf for most of the times. For example, the
