http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56564
Bug #: 56564
Summary: [4.7 Regression] movdqa on possibly-8-byte-aligned
struct with -O3
Classification: Unclassified
Product: gcc
Version: 4.7.2
Status: UN
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56564
--- Comment #1 from lukeocamden at gmail dot com 2013-03-07 16:26:39 UTC ---
Created attachment 29611
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29611
Preprocessed source file
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56564
--- Comment #3 from lukeocamden at gmail dot com 2013-03-08 10:32:34 UTC ---
Sorry for my cryptic comments about the "other object file". It's compiled with
icc 13. I will attach the preprocessed source and generated assembly.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56564
--- Comment #4 from lukeocamden at gmail dot com 2013-03-08 10:47:10 UTC ---
Created attachment 29618
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29618
Preprocessed with ICC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56564
--- Comment #5 from lukeocamden at gmail dot com 2013-03-08 11:07:45 UTC ---
Created attachment 29619
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29619
Generated by icc 13
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54420
Bug #: 54420
Summary: Segmentation in decl_mangling_context
Classification: Unclassified
Product: gcc
Version: 4.7.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53802
Bug #: 53802
Summary: Spurious 'may be used uninitialized' related to shifts
Classification: Unclassified
Product: gcc
Version: 4.7.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lukeocamden at gmail dot com
Sorry: no preprocessed source yet.
$ g++ --version
g++ (GCC) 4.9.0 20140202 (experimental)
Copyright (C) 2014 Free Software Foundation, Inc.
This is free
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639
Bug 24639 depends on bug 53802, which changed state.
Bug 53802 Summary: Spurious 'may be used uninitialized' related to shifts
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53802
What|Removed |Added
---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53802
lukeocamden at gmail dot com changed:
What|Removed |Added
Status|NEW |RESOLVED
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: lukeocamden at gmail dot com
Seems like std::function only manages to avoid malloc for function pointers,
but not for small objects.
$ g++ --version
g++ (GCC) 4.10.0 20140720 (experimental
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61909
--- Comment #2 from lukeocamden at gmail dot com ---
(In reply to Jonathan Wakely from comment #1)
> This is by design.
I don't really follow - do you mean a consequence of the design, or does the
standard mandate copying/moving the obj
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61909
--- Comment #4 from lukeocamden at gmail dot com ---
(In reply to Jonathan Wakely from comment #3)
> (In reply to lukeocamden from comment #2)
> > (In reply to Jonathan Wakely from comment #1)
> > > This is by design.
>
onent: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: lukeocamden at gmail dot com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
Hello,
I have not seen this before!
$ echo 'int main() { }' | g++ -g0 -ggdb -flto -xc++ -
/usr/bin/ld: /
14 matches
Mail list logo