[Bug c++/119848] New: Concept check makes it impossible to return types that depend on the type being defined

2025-04-17 Thread jpakkane at gmail dot com via Gcc-bugs
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jpakkane at gmail dot com Target Milestone: --- This might not be a bug in GCC itself, but in the C++ specification. The behaviour is the same for Clang and

[Bug c++/105467] Dependency file produced by C++ modules causes Ninja errors

2023-12-30 Thread jpakkane at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105467 --- Comment #6 from jpakkane at gmail dot com --- According to C++ foundation's developer survey [1] the most popular build system for C++ projects is CMake by quite a massive margin. Based on personal experience almost everybody uses CM

[Bug c++/105467] Dependency file produced by C++ modules causes Ninja errors

2023-12-30 Thread jpakkane at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105467 --- Comment #4 from jpakkane at gmail dot com --- As a build system developer I'd like that the most common usage (i.e. using Ninja) would be the default and work without extra compiler flags.

[Bug c++/105467] Dependency file produced by C++ modules causes Ninja errors

2023-10-20 Thread jpakkane at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105467 --- Comment #2 from jpakkane at gmail dot com --- It would be preferable to have the default work out of the box than having every end user having to add compiler flags to make things work. Ninja is the most popular underlying build system for

[Bug c++/105467] New: Dependency file produced by C++ modules causes Ninja errors

2022-05-03 Thread jpakkane at gmail dot com via Gcc-bugs
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jpakkane at gmail dot com Target Milestone: --- Currently if you try to build C++ modules using Ninja and a dependency file, things fail with this fairly cryptic error message (that comes

[Bug c++/84544] New: Missing warning when returning a reference to internal variable inside a lambda

2018-02-24 Thread jpakkane at gmail dot com
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jpakkane at gmail dot com Target Milestone: --- Suppose you have a C++14 method like this: auto f1() { int x = 3; auto l = [&]() -> int& { return x; };

[Bug other/84351] New: Provide dependency information also when linking

2018-02-12 Thread jpakkane at gmail dot com
: other Assignee: unassigned at gcc dot gnu.org Reporter: jpakkane at gmail dot com Target Milestone: --- The -M flag and its like is very useful for reliable dependencies. It would be great if the same would work also when linking. The use case is the following. Suppose you

[Bug c++/82763] New: std::is_pod works incorrectly with volatile

2017-10-28 Thread jpakkane at gmail dot com
++ Assignee: unassigned at gcc dot gnu.org Reporter: jpakkane at gmail dot com Target Milestone: --- The following program prints "is_pod 1": #include #include #include typedef struct { int64_t dt_us; } __attribute__ ((packed)) mytime_t ; struct

[Bug other/81541] New: Potential size optimisation: reusing common function endings

2017-07-24 Thread jpakkane at gmail dot com
Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: jpakkane at gmail dot com Target Milestone: --- In embedded development code size optimizations are very important and there are some optimizations that commercial compilers do but GCC

[Bug c++/78773] "Empty" const only class not optimized away

2016-12-12 Thread jpakkane at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78773 --- Comment #2 from jpakkane at gmail dot com --- I tried constexpr and it did not have any effect so I just left it out for simplicity. Sorry for the dupe. I tried searching but could not come up with a suitable search term to find it.

[Bug c++/78773] New: "Empty" const only class not optimized away

2016-12-12 Thread jpakkane at gmail dot com
ty: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jpakkane at gmail dot com Target Milestone: --- Suppose we have the following very simple class for accessing a memory mapped register: class MemoryMappedRegister

[Bug c++/77307] New: Bring memset + free optimisation to C++

2016-08-21 Thread jpakkane at gmail dot com
++ Assignee: unassigned at gcc dot gnu.org Reporter: jpakkane at gmail dot com Target Milestone: --- For the following code gcc will remove the call to memset: void destroy(char *buf, size_t bufsize) { memset(buf, 0, bufsize); free(buf); } However if you change it to

[Bug fortran/62162] Gfortran produces incorrect dependency files when using -MQ

2014-08-16 Thread jpakkane at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62162 --- Comment #4 from jpakkane at gmail dot com --- That seems the reasonable thing to do. Hopefully someone looks into this soon.

[Bug fortran/62162] Gfortran produces incorrect dependency files when using -MQ

2014-08-16 Thread jpakkane at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62162 --- Comment #2 from jpakkane at gmail dot com --- Seems to be. There are some claims that it would be fixed in 4.6 but as the comments state, is still around in 4.9.

[Bug fortran/62162] New: Gfortran produces incorrect dependency files when using -MQ

2014-08-16 Thread jpakkane at gmail dot com
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: jpakkane at gmail dot com Create a simple Fortran file stuff.f95 that looks like this: MODULE Circle REAL, PARAMETER :: Pi = 3.1415927 REAL :: radius END MODULE Circle Then compile

[Bug c++/61113] Mark private methods hidden automatically

2014-05-08 Thread jpakkane at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61113 --- Comment #2 from jpakkane at gmail dot com --- In that case it would fail. But you can make it work by doing this (assuming compilation with -fvisibility=hidden): class __attribute__ ((visibility("default"))) Thing final { publ

[Bug c++/61113] New: Mark private methods hidden automatically

2014-05-08 Thread jpakkane at gmail dot com
++ Assignee: unassigned at gcc dot gnu.org Reporter: jpakkane at gmail dot com Suppose you compile a class defined like this using -fvisibility=hidden: class __attribute__ ((visibility("default"))) Thing final { public: void publicFunc(); private: void p

[Bug lto/58251] -flto causes ICE lto1: internal compiler error: in splice_child_die, at dwarf2out.c:4706

2013-12-05 Thread jpakkane at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58251 --- Comment #5 from jpakkane at gmail dot com --- I retried this with Gcc 4.8.2 on trusty and no longer get the crash. I have not tried to reproduce David Kredba's issue so that might still remain.

[Bug lto/58251] New: -flto causes ICE lto1: internal compiler error: in splice_child_die, at dwarf2out.c:4706

2013-08-27 Thread jpakkane at gmail dot com
Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: jpakkane at gmail dot com With Gcc 4.8.1 on Ubuntu Saucy x86-64 I can reliably trigger an ICE. As the issue happens during link, I can't reduce it to a single

[Bug c++/54780] G++ does not find precompiled headers in some cases

2012-10-03 Thread jpakkane at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54780 --- Comment #3 from jpakkane at gmail dot com 2012-10-03 07:53:59 UTC --- Thanks for the explanation and workaround. I guess this is not a big issue if you are using Autotools, where the established practice is to compile inside the

[Bug c++/54780] New: G++ does not find precompiled headers in some cases

2012-10-02 Thread jpakkane at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54780 Bug #: 54780 Summary: G++ does not find precompiled headers in some cases Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: norma