[Bug c++/80242] [C++17+] "Trailing return types" with "non-type template arguments" which could be "constant expressions" produce a parsing error

2023-06-22 Thread roland at rschulz dot eu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80242 Roland Schulz changed: What|Removed |Added CC||roland at rschulz dot eu --- Comment #2

[Bug c++/98936] [DR1734] Incorrect computation of trivially copyable for class with user-declared move assignment operator, defined as deleted

2021-11-01 Thread roland at rschulz dot eu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98936 Roland Schulz changed: What|Removed |Added CC||roland at rschulz dot eu --- Comment #2

[Bug c++/96288] New: [DR 1734] __is_trivial and __is_tirivil_copyable fails for deleted members

2020-07-22 Thread roland at rschulz dot eu
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: roland at rschulz dot eu Target Milestone: --- https://godbolt.org/z/snjof8 The resolution of 1734 requires the class: - has at least one non-deleted copy constructor, move

[Bug c++/94628] New: segfault decltype

2020-04-16 Thread roland at rschulz dot eu
: unassigned at gcc dot gnu.org Reporter: roland at rschulz dot eu Target Milestone: --- GCC 9.3 and trunk. Internal compiler error: Segmentation fault #include #include template using int_constant = std::integral_constant; template auto select(int i, F&&f, Args&&...a

[Bug libstdc++/91371] std::bind and bind_front don't work with function with call convention

2019-08-06 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91371 --- Comment #4 from Roland Schulz --- Are there any known issues with the libc++ solution? Otherwise it seems like the simpler solution than adding a builtin.

[Bug libstdc++/91371] std::bind and bind_front don't work with function with call convention

2019-08-06 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91371 --- Comment #2 from Roland Schulz --- Would you recommend to fix this by adding the specializations for the alternative calling conventions to std::is_function or by switching to the libc++ approach?

[Bug libstdc++/91371] New: std::bind and bind_front don't work with function with call convention

2019-08-05 Thread roland at rschulz dot eu
ormal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: roland at rschulz dot eu Target Milestone: --- If a function with call convention function type attribute is passed to bind/bind_front it fails. Reproducer: #include

[Bug libstdc++/87020] New: comparison operator isn't called for stateless allocator without is_always_equal for C++11/14

2018-08-19 Thread roland at rschulz dot eu
IRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: roland at rschulz dot eu Target Milestone: --- For an empty allocator the comparison operators aren't used, unless is_always_equal=std::fal

[Bug c++/83936] [feature request] Allow constexpr char* as target argument

2018-01-18 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83936 --- Comment #2 from Roland Schulz --- Do you mean for the target attribute or for all attributes in general? The following example suggests that for the alloc_align attribute it works to have the argument depend on a template argument. template

[Bug c++/83936] New: [feature request] Allow constexpr char* as target argument

2018-01-18 Thread roland at rschulz dot eu
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: roland at rschulz dot eu Target Milestone: --- It would be very useful to be able to specify a "constexpr const char*const" string as an argument to the target attribute. This woul

[Bug middle-end/49363] [feature request] multiple target attribute (and runtime dispatching based on cpuid)

2018-01-18 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49363 Roland Schulz changed: What|Removed |Added CC||roland at rschulz dot eu --- Comment

[Bug c++/83875] [feature request] target_clones compatible SIMD capability/length check

2018-01-18 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83875 --- Comment #8 from Roland Schulz --- I would suggest that: - inside multi-versioned (target_clones/target) function it depends on the active target - inside a constexpr context (function/variable, your examples) or always_inline function it depe

[Bug c++/83875] [feature request] target_clones compatible SIMD capability/length check

2018-01-17 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83875 --- Comment #5 from Roland Schulz --- (In reply to Jakub Jelinek from comment #4) > So we are essentially talking about a builtin like > __builtin_cpu_{is,supports}, that instead of runtime check would query the > target flags of the containing f

[Bug c++/83875] [feature request] target_clones compatible SIMD capability/length check

2018-01-16 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83875 --- Comment #3 from Roland Schulz --- Instead of adding (/modifying) the goal could also be achieved by allowing to call a target+constexpr function from a target_clone function. Currently this gives: "error: call to non-constexpr function" (exam

[Bug c++/83911] New: ICE with target attribute on constructor in gimplify_expr at gimplify.c:11321

2018-01-16 Thread roland at rschulz dot eu
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: roland at rschulz dot eu Target Milestone: --- Target: x86-64 > g++ test_target2_min.cc -c test_target2_min.cc: In function 'SimdF

[Bug c++/83875] [feature request] target_clones compatible SIMD capability/length check

2018-01-16 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83875 --- Comment #2 from Roland Schulz --- The main problem is that it already gets resolved in the preprocessor stage. Thus if you have: __attribute__((target_clones("avx","default"))) void foo(){ #if __AVX__ ... #endif } , it doesn

[Bug other/83876] New: [feature request] flag to force vague linkage for typeinfo and/or disable vtable anchoring

2018-01-15 Thread roland at rschulz dot eu
Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: roland at rschulz dot eu Target Milestone: --- Vague linking is required for runtime binding [1] and RTTI to work together. If vtable anchoring is possible

[Bug c++/83875] New: [feature request] target_clones compatible SIMD capability/length check

2018-01-15 Thread roland at rschulz dot eu
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: roland at rschulz dot eu Target Milestone: --- Currently there are two methods to check for SIMD capabilities (e.g. AVX). The preprocessor defines (e.g. __AVX__) and the builtin

[Bug c++/81957] New: ICE decltype

2017-08-23 Thread roland at rschulz dot eu
at gcc dot gnu.org Reporter: roland at rschulz dot eu Target Milestone: --- #include struct f { template void operator()(std::integral_constant, Int i) { } }; template auto dispatch(F f, T...t) -> decltype(f(std::integral_constant()..., t...)) { return f(

[Bug target/54412] Request for 32-byte stack alignment with -mavx on Windows

2015-09-23 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412 --- Comment #13 from Roland Schulz --- But this problem is limited to GCC. ICC, Clang and MSVC don't have the problem with compiling 64bit AVX code. Thus they must have some kind of work-around for ABI and GCC should be able to use a work-around

[Bug target/54412] Request for 32-byte stack alignment with -mavx on Windows

2014-09-19 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412 --- Comment #10 from Roland Schulz --- Created attachment 33520 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33520&action=edit Slightly modified testcase This slightly modified testcase in which the return value isn't stored, still segfa

[Bug target/54412] Request for 32-byte stack alignment with -mavx on Windows

2014-09-04 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412 --- Comment #7 from Roland Schulz --- For me the problem isn't fixed with gcc 4.9.1. I tried two build a) http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/mingw-w64-install.e

[Bug target/49001] GCC uses VMOVAPS/PD AVX instructions to access stack variables that are not 32-byte aligned

2014-09-03 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49001 --- Comment #4 from Roland Schulz --- *** Bug 61730 has been marked as a duplicate of this bug. ***

[Bug target/61730] Cygwin AVX __m256i return value misaligned

2014-09-03 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61730 Roland Schulz changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/54412] Request for 32-byte stack alignment with -mavx on Windows

2014-09-03 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412 --- Comment #5 from Roland Schulz --- This seems to me to be a duplicate of 49001.

[Bug target/61730] Cygwin AVX __m256i return value misaligned

2014-09-01 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61730 --- Comment #1 from Roland Schulz --- It is probably a duplicate of 54412 or 49001 (which seem duplicates of each other). The bugs I found previous where about 16-byte alignment and that has been fixed. But the 32-byte alignment required for AVX

[Bug sanitizer/55561] TSAN: provide a TSAN instrumented libgomp

2014-07-08 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561 --- Comment #50 from Roland Schulz --- I must say I don't know how the internals work. But I assume that reductions are implemented in libgomp (I know they are in iomp). Thus for any code which uses OpenMP reduce statements, libgomp would touch u

[Bug target/61730] New: Cygwin AVX __m256i return value misaligned

2014-07-06 Thread roland at rschulz dot eu
: target Assignee: unassigned at gcc dot gnu.org Reporter: roland at rschulz dot eu Created attachment 33079 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33079&action=edit Testcase which segfaults on Cygwin because of incorrect alignment The attached testcase segfault c

[Bug sanitizer/55561] TSAN: provide a TSAN instrumented libgomp

2014-05-14 Thread roland at rschulz dot eu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561 --- Comment #47 from Roland Schulz --- Using 4.9 and --disable-linux-futex I don't get any false positives. Thus the problem I saw with 4.8.2 is indeed fixed with 4.9. Thanks! What is the advantage of a TSAN instrumented libgomp over one with --

[Bug sanitizer/55561] TSAN: provide a TSAN instrumented libgomp

2014-05-08 Thread roland at rschulz dot eu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561 Roland Schulz changed: What|Removed |Added CC||roland at rschulz dot eu --- Comment #44

[Bug gcov-profile/47618] Collecting multiple profiles and using all for PGO

2012-07-24 Thread roland at rschulz dot eu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47618 --- Comment #11 from Roland Schulz 2012-07-25 00:50:30 UTC --- Steven wrote that they are not merged but that race conditions occur. That is also what I observed. To clarify: Message Passing Interface (MPI) is a parallelization method which execu

[Bug gcov-profile/47618] Collecting multiple profiles and using all for PGO

2012-07-24 Thread roland at rschulz dot eu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47618 --- Comment #9 from Roland Schulz 2012-07-24 23:52:41 UTC --- I think a tool to merge would be a good partial solution. As far as I can see what would still be missing for user-friendly usage, is a mechanism to guarantee that all pre-merged file

[Bug gcov-profile/47618] New: Collecting multiple profiles and using all for PGO

2011-02-05 Thread roland at rschulz dot eu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47618 Summary: Collecting multiple profiles and using all for PGO Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: gcov-profile