date:20180113

[Bug libfortran/83811] fortran 'e' format broken for single digit exponents

2018-01-13 Thread jvdelisle at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83811

Jerry DeLisle  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
   Last reconfirmed||2018-01-14
   Assignee|unassigned at gcc dot gnu.org  |jvdelisle at gcc dot 
gnu.org
 Ever confirmed|0   |1

--- Comment #3 from Jerry DeLisle  ---
Further investigation is showing me that the buffer containing the float string
is wrong before it goes into build_float_string.  Ths means it has something to
do with snprintf.

In the wrong output case with write(s, '(1pe5.0e1)') 1.e-4, the buffer contains
"+1.e-0" with nprinted=7. This indicates we have an off by 1 like error here.

[Bug target/80870] [7 Regression] ICE building 7.1.0 sh-elf crosscompiler on macOS

2018-01-13 Thread Anders.Montonen at iki dot fi

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80870

--- Comment #3 from Anders Montonen  ---
Current GCC 7 branch (r256652) fails with the "fancy_abort" errors from bug
82091 using Xcode 9.2 (clang-900.0.39.2). GCC 7.2.0 and trunk fail with the
same errors.

In file included from ../../gcc/gcc/config/sh/sh_optimize_sett_clrt.cc:30:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/vector:266:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/__bit_reference:15:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/algorithm:640:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/memory:629:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/typeinfo:205:2:
error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean
simply 'fancy_abort'?
_VSTD::abort();
^~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/__config:392:15:
note: expanded from macro '_VSTD'
#define _VSTD std::_LIBCPP_NAMESPACE
  ^
../../gcc/gcc/system.h:725:13: note: 'fancy_abort' declared here
extern void fancy_abort (const char *, int, const char *) ATTRIBUTE_NORETURN;
^
In file included from ../../gcc/gcc/config/sh/sh_optimize_sett_clrt.cc:30:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/vector:266:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/__bit_reference:15:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/algorithm:640:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/memory:639:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/stdexcept:195:4:
error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean
simply 'fancy_abort'?
  _VSTD::abort();
  ^~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/__config:392:15:
note: expanded from macro '_VSTD'
#define _VSTD std::_LIBCPP_NAMESPACE
  ^
../../gcc/gcc/system.h:725:13: note: 'fancy_abort' declared here
extern void fancy_abort (const char *, int, const char *) ATTRIBUTE_NORETURN;
^
In file included from ../../gcc/gcc/config/sh/sh_optimize_sett_clrt.cc:30:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/vector:266:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/__bit_reference:15:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/algorithm:640:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/memory:639:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/stdexcept:206:4:
error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean
simply 'fancy_abort'?
  _VSTD::abort();
  ^~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/__config:392:15:
note: expanded from macro '_VSTD'
#define _VSTD std::_LIBCPP_NAMESPACE
  ^
../../gcc/gcc/system.h:725:13: note: 'fancy_abort' declared here
extern void fancy_abort (const char *, int, const char *) ATTRIBUTE_NORETURN;
^
In file included from ../../gcc/gcc/config/sh/sh_optimize_sett_clrt.cc:30:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/vector:266:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/__bit_reference:15:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/algorithm:640:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/memory:639:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/stdexcept:217:4:
error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean
simply 'fancy_abort'?
  _VSTD::abort();
  ^~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/__config:392:15:
note: expanded from macro '_VSTD'
#define _VSTD std::_LIBCPP_NAMESPACE

[Bug tree-optimization/83819] [meta-bug] missing strlen optimizations

2018-01-13 Thread egallager at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83819

Eric Gallager  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2018-01-14
 CC||egallager at gcc dot gnu.org
 Ever confirmed|0   |1

--- Comment #1 from Eric Gallager  ---
Confirmed that this is a useful meta-bug grouping.

[Bug libstdc++/83601] std::regex_replace C++14 conformance issue: escaping in SED mode

2018-01-13 Thread timshen at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83601

Tim Shen  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Tim Shen  ---
Mark as fixed.

[Bug libstdc++/83601] std::regex_replace C++14 conformance issue: escaping in SED mode

2018-01-13 Thread timshen at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83601

--- Comment #2 from Tim Shen  ---
Author: timshen
Date: Sun Jan 14 00:48:30 2018
New Revision: 256654

URL: https://gcc.gnu.org/viewcvs?rev=256654=gcc=rev
Log:
PR libstdc++/83601
* include/bits/regex.tcc (regex_replace): Fix escaping in sed.
* testsuite/28_regex/algorithms/regex_replace/char/pr83601.cc: Tests.
* testsuite/28_regex/algorithms/regex_replace/wchar_t/pr83601.cc:
Tests.

Added:
   
trunk/libstdc++-v3/testsuite/28_regex/algorithms/regex_replace/char/pr83601.cc
   
trunk/libstdc++-v3/testsuite/28_regex/algorithms/regex_replace/wchar_t/pr83601.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/bits/regex.tcc

[Bug c++/83588] [6/7/8 Regression] struct with two flexible arrays causes an internal compiler error

2018-01-13 Thread msebor at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83588

Martin Sebor  changed:

   What|Removed |Added

   Keywords|accepts-invalid |
 Status|UNCONFIRMED |NEW
   Last reconfirmed||2018-01-14
 CC||msebor at gcc dot gnu.org
Summary|Struct with two flexible|[6/7/8 Regression] struct
   |arrays causes an internal   |with two flexible arrays
   |compiler error  |causes an internal compiler
   ||error
 Ever confirmed|0   |1
  Known to fail||6.4.0, 7.2.0, 8.0

--- Comment #1 from Martin Sebor  ---
Confirmed with GCC 6, 7, and 8.  Bisection points to r231665.  Initialization
of objects with flexible array members is accepted for compatibility with GCC.

$ cat pr83588.C && gcc -S -Wall pr83588.C.

struct Foo  
{
  int i, a[], b[];
};  

struct Foo t = {1, {0, 0, 0}, {0, 0, 0}}; 
pr83588.C:6:41: internal compiler error: in output_constructor_regular_field,
at varasm.c:5155
 struct Foo t = {1, {0, 0, 0}, {0, 0, 0}};
 ^
0x16c5a99 output_constructor_regular_field
/ssd/src/gcc/git/gcc/varasm.c:5155
0x16c6729 output_constructor
/ssd/src/gcc/git/gcc/varasm.c:5438
0x16c5090 output_constant
/ssd/src/gcc/git/gcc/varasm.c:4965
0x16baa3d assemble_variable_contents
/ssd/src/gcc/git/gcc/varasm.c:2134
0x16bb549 assemble_variable(tree_node*, int, int, int)
/ssd/src/gcc/git/gcc/varasm.c:2310
0x16d555e varpool_node::assemble_decl()
/ssd/src/gcc/git/gcc/varpool.c:590
0xcad84b output_in_order
/ssd/src/gcc/git/gcc/cgraphunit.c:2385
0xcae001 symbol_table::compile()
/ssd/src/gcc/git/gcc/cgraphunit.c:2623
0xcae2c1 symbol_table::finalize_compilation_unit()
/ssd/src/gcc/git/gcc/cgraphunit.c:2717
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See  for instructions.

[Bug libstdc++/83830] New: has_unique_object_representations_v is missing

2018-01-13 Thread rs2740 at gmail dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83830

Bug ID: 83830
   Summary: has_unique_object_representations_v is missing
   Product: gcc
   Version: 8.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: libstdc++
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rs2740 at gmail dot com
  Target Milestone: ---

libstdc++ has the trait but not the _v form, which was added by the editor per
NB comment US-9 on the C++17 CD, see
https://github.com/cplusplus/draft/commit/97058f9cc925cd9a9e818545cad4e1c198d714cb.

[Bug c++/83596] ['17] can't use member pointer result of a constexpr function as template argument

2018-01-13 Thread msebor at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83596

Martin Sebor  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2018-01-14
 CC||msebor at gcc dot gnu.org
 Ever confirmed|0   |1

--- Comment #1 from Martin Sebor  ---
Without studying this too deeply I'll confirm this report based on other
compilers (including Clang, EDG, and MSVC) accepting the code.

[Bug c++/83614] deduction failure for template-template argument with trailing template parameter pack

2018-01-13 Thread msebor at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83614

Martin Sebor  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2018-01-13
 CC||msebor at gcc dot gnu.org
 Ever confirmed|0   |1
  Known to fail||5.4.0, 6.4.0, 7.2.0, 8.0

--- Comment #1 from Martin Sebor  ---
Confirmed.  All recent GCC versions reject the snippet with the error below
(please remember to include compiler output in bug reports about diagnostics --
see https://gcc.gnu.org/bugs for details).  Other compilers besides Clang
compile the code (EDG and MSVC).

pr83614.C: In function ‘int main()’:
pr83614.C:18:10: error: no matching function for call to ‘foo(Y&)’
 foo(y); // error: X does not match A
  ^
pr83614.C:10:6: note: candidate: ‘template

58 matches

Mail list logo