http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56746
Bug #: 56746
Summary: 4.8 regression: increased memory usage when compiling
C++
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56746
--- Comment #2 from Mathias Gaunard 2013-03-27
11:04:08 UTC ---
The preprocessed file is 7 megabytes, which exceeds what I can attach here.
I do not think it is practical to reduce it with automatic tools.
Would it be ok to provide it as-i
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56746
--- Comment #5 from Mathias Gaunard 2013-03-27
16:41:16 UTC ---
While trying to isolate the problem, I have observed that the problem does not
occur if -save-temps is used.
While using -save-temps does not change anything with GCC 4.7, usi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56746
--- Comment #7 from Mathias Gaunard 2013-03-28
10:39:53 UTC ---
Using either -save-temps or -ftrack-macro-expansion=0-ftrack-macro-expansion=0
removes the memory hog.
Compiling the preprocessed source does not cause increased memory usage.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57057
Bug #: 57057
Summary: Bad optimization on x86 for minps and maxps
Classification: Unclassified
Product: gcc
Version: 4.7.2
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57057
--- Comment #1 from Mathias Gaunard 2013-04-24
16:42:23 UTC ---
Created attachment 29931
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29931
bad optimisation testcase
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50800
--- Comment #6 from Mathias Gaunard 2012-08-14
10:53:07 UTC ---
I've had this happen with 4.7.1 without any may_alias involved.
Why is this bug still marked 'waiting'? Are more testcases necessary?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54436
Bug #: 54436
Summary: Compiling some regular C++ code gives assembler
'700415 shortened to 255' warning
Classification: Unclassified
Product: gcc
Version: 4.7.1
Statu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54436
--- Comment #3 from Mathias Gaunard 2012-09-01
01:23:04 UTC ---
While a warning is emitted, is the code in the end still valid or is that a
miscompilation?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55184
Bug #: 55184
Summary: Invalid codegen with vectors and casts
Classification: Unclassified
Product: gcc
Version: 4.6.3
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55184
--- Comment #1 from Mathias Gaunard 2012-11-03
00:29:47 UTC ---
Problem seems to occur with i686 as well but only if SSE2 is enabled (you'll
need to replace 'long' by 'long long' for this in the testcase)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55184
Mathias Gaunard changed:
What|Removed |Added
Attachment #28600|0 |1
is obsolete|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55184
--- Comment #4 from Mathias Gaunard 2012-11-04
18:01:27 UTC ---
Sorry, I edited the file in between and ended up uploading the wrong test case.
Below is the result on my machine with the fixed testcase.
$ gcc --version
gcc (Ubuntu/Lin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56746
--- Comment #11 from Mathias Gaunard ---
4.8.1 is still affected by this.
I wouldn't say it's NOTABUG if a new diagnostic feature enabled by default
increases memory consumption by 50%, even when no diagnostic is emitted.
I cannot easily give a
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56746
--- Comment #12 from Mathias Gaunard ---
This may be considered a duplicate of #53525, though that bug is more focused
on performance than memory usage.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53525
Mathias Gaunard changed:
What|Removed |Added
CC||mathias at gaunard dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53525
--- Comment #18 from Mathias Gaunard ---
I'm not competent enough to make my own builds of GCC with patches, and I
unfortunately do not have much time to contribute to this either.
If someone can give me binaries for debian x86-64 I can do some t
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50396
Bug #: 50396
Summary: SSE division by zero generates incorrect code with
optimizations enabled
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCO
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50495
Bug #: 50495
Summary: Optimize exact matches in overload resolution
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50495
--- Comment #2 from Mathias Gaunard 2011-09-23
15:46:50 UTC ---
Would you happen to have a reference to those changes or discussed
improvements?
I'm not testing with a very recent GCC.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50495
--- Comment #5 from Mathias Gaunard 2011-09-23
16:38:11 UTC ---
clang was already 50% faster in my tests, so I guess that will put gcc 4.7 on
par with it.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50495
--- Comment #7 from Mathias Gaunard 2011-09-23
17:56:48 UTC ---
Created attachment 25349
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25349
Python script to generate C++ files with many overloads
Syntax is
./generate.py [use single functi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50495
--- Comment #8 from Mathias Gaunard 2011-09-23
17:58:41 UTC ---
Created attachment 25350
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25350
Bash script to more easily drive python script
Same usage as generate.py, but doesn't take the fir
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50800
Bug #: 50800
Summary: Internal compiler error in finish_member_declarations,
possibly related to may_alias attribute
Classification: Unclassified
Product: gcc
Version: 4.6.1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50800
--- Comment #1 from Mathias Gaunard 2011-10-19
18:20:06 UTC ---
Testcase is here (couldn't attach it due to bugzilla size restrictions):
http://mathias.gaunard.com/data/ice_finish_member_declaration.cpp
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50396
--- Comment #1 from Mathias Gaunard 2011-10-20
08:58:19 UTC ---
This bug has stayed as unconfirmed for a while.
Is there anything that I could do to help?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50800
--- Comment #3 from Mathias Gaunard 2011-10-20
20:07:24 UTC ---
Created attachment 25562
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25562
Reduced testcase
Original testcase reduced using automated delta tools
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51654
Bug #: 51654
Summary: C++ preprocessor bug with -maltivec and typedefs
involving 'vector'
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIRM
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51654
--- Comment #1 from Mathias Gaunard 2011-12-22
15:16:18 UTC ---
Excuse the typo, the above code should have been
template
struct test
{
typedef typename T::vector vector;
};
to be valid C++ code.
The " vector" bit is incorrectly removed in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51654
--- Comment #3 from Mathias Gaunard 2011-12-22
15:54:20 UTC ---
The workarounds
#undef vector
or
compiling with -Dvector=vector
seem to work.
But shouldn't this not be necessary when altivec.h is not included?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51654
--- Comment #5 from Mathias Gaunard 2011-12-22
18:48:36 UTC ---
gaunard@emeria:~$ g++-4.6 -v
Using built-in specs.
COLLECT_GCC=g++-4.6
COLLECT_LTO_WRAPPER=/usr/lib/gcc/powerpc-linux-gnu/4.6.0/lto-wrapper
Target: powerpc-linux-gnu
Configured with:
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mathias at gaunard dot com
Target Milestone: ---
As of GCC 8.2, the following code is well-formed:
auto const f = [](int) __attribute__((always_inline)) -> int { return 0; };
With
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90489
--- Comment #1 from Mathias Gaunard ---
Possibly related,
Both
auto const f = [](int) [[gnu::always_inline]] -> int { return 0; };
and
auto const f = [](int) [[gnu::always_inline]] { return 0; };
also fail with GCC 9.1, but work with GCC 8.2.
s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51654
Mathias Gaunard changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
IRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mathias at gaunard dot com
Target Milestone: ---
Since C++17, lambdas are automatically constexpr whenever they can.
It seems however that GCC 7.1 tries to make la
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mathias at gaunard dot com
Target Milestone: ---
Building the following code with std=c++1z
#include
template
struct traits
{
static constexpr T const_min = 0
36 matches
Mail list logo
