https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72865
--- Comment #2 from Aleksej Lebedev ---
Just tried it with gcc-6.0.0 under DragonflyBSD. It seems that the bug is
fixed.
$ uname -a
DragonFly kl.zta.lk 4.4-RELEASE DragonFly v4.4.3.1.gf6df7-RELEASE #8: Thu Apr
21 17:59:21 CEST 2016 r...@kl.z
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72865
--- Comment #1 from Aleksej Lebedev ---
Forgot to tell what platform I'm running this:
$ uname -a
Linux zhtw-pc 4.2.0-41-generic #48-Ubuntu SMP Fri Jun 24 11:28:43 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Exact version of the GCC:
$ g++ --version
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: root at zta dot lk
Target Milestone: ---
The following (correct) code triggers a compilation error when compiled with
gcc. It does compiles under clang.
Removing __attribute__((__may_alias__
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63386
--- Comment #7 from TechoMan ---
https://github.com/bulletphysics/bullet3/blob/master/src/BulletCollision/CollisionDispatch/btInternalEdgeUtility.cpp
<- that file. For 3.x line would be 310 , '{'.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63386
--- Comment #5 from TechoMan ---
TDM version - gcc version 4.8.1 (tdm-2)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63386
--- Comment #4 from TechoMan ---
gcc version 4.8.1 (GCC).
Why CB release - that error was only on release of CB. It changes some
variables , such as -O2. Originaly it was rel. CB, but i found what its O2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63386
--- Comment #2 from TechoMan ---
-O2 causes that , -O1 doesnt.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63386
--- Comment #1 from TechoMan ---
Using latests MinGW & TDM.
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: root at borealis dot su
mingw32-g++.exe -Wall -fexceptions -O2 -I..\Bullet\src -c
C:\CProj\Bullet\src\BulletCollision\CollisionDispatch\btInternalEdgeUtility.cpp
-o
obj\Release\Bullet\src\BulletCollision\CollisionDispatch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57754
--- Comment #1 from Heiher ---
Created attachment 30409
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30409&action=edit
Patch
Assignee: unassigned at gcc dot gnu.org
Reporter: root at heiher dot info
Loongson 3A is MIPS64R2-compatible, so this means that it should based
on ISA_MIPS64R2 (not ISA_MIPS64) ?
References:
http://www.loongson.cn/uploadfile/201204
--- Comment #6 from smal dot root at gmail dot com 2010-03-09 01:02 ---
Well, I will make necessary tests
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43104
--- Comment #4 from smal dot root at gmail dot com 2010-03-08 21:49 ---
> I still cannot reproduce the error
you got
>>lds r24, 0x
that is error!
address of variable is NULL. Address of
volatile uint8_t SomeVariable
cant be NULL in any case.
--
Data Memor
--- Comment #2 from smal dot root at gmail dot com 2010-03-08 21:15 ---
(In reply to comment #1)
> I cannot reproduce the problem.
>
>c: 80 91 00 00 lds r24, 0x
Its mean load data from SRAM at address 0x. Variable (in our case
mUsart0BufferReadPtr) ha
Product: gcc
Version: 4.4.3
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: smal dot root at gmail dot com
GCC host triplet: Win32
GCC target triplet
--- Comment #2 from smal dot root at gmail dot com 2009-09-20 17:30 ---
I correct clock, restart Xorg and everything work... Its good. Sorry
--
smal dot root at gmail dot com changed:
What|Removed |Added
defines(-D) are not working with include(-
I)
Product: gcc
Version: 4.3.3
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: s
--- Comment #2 from root at WPI dot EDU 2005-12-14 15:35 ---
Created an attachment (id=10487)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10487&action=view)
the file that breaks gfortran 4.0.2, for easier retrieval
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25412
Here is the file.
Please, read the document.
20 matches
Mail list logo
