https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71011
Pranith Kumar changed:
What|Removed |Added
CC||bobby.prani at gmail dot com
mponent: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: bobby.prani at gmail dot com
Target Milestone: ---
I am getting a warning that "data" may be uninitialized. But there is no such
variable being used anywhere.
src/allocate.cc: In member function ‘void allocate_c:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71011
--- Comment #2 from Pranith Kumar ---
Created attachment 38444
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38444&action=edit
pre-procssed source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71011
--- Comment #3 from Pranith Kumar ---
Command which shows this error:
$ g++ -o .opt_build/src/allocate.o -c -O3 -std=c++11 -funroll-loops -Werror
-Wuninitialized -Wno-write-strings -DLONG_COUNTERS -DNO_MPI -DNO_DEBUG
src/allocate.i -Wall -Wextra
: c
Assignee: unassigned at gcc dot gnu.org
Reporter: bobby.prani at gmail dot com
Target Milestone: ---
GCC does not correctly point out the unknown escape sequence in the string
being printed.
#include
int main()
{
fprintf(stderr, "This statement
: c
Assignee: unassigned at gcc dot gnu.org
Reporter: bobby.prani at gmail dot com
Target Milestone: ---
Created attachment 35507
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35507&action=edit
Enable O3 optimization
Linux kernel 4.1-rc1 fails to boot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66083
--- Comment #1 from Pranith Kumar ---
Created attachment 35508
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35508&action=edit
config file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66083
--- Comment #3 from Pranith Kumar ---
The kernel fails to boot. It works using 4.7/4.8 but 4.9 does not work. Not
sure what you mean which file. How do I pin point that?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63375
--- Comment #11 from Pranith Kumar ---
Is there any work around for this in the mean time? Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63375
--- Comment #13 from Pranith Kumar ---
The main concern here is moving the read past the fence instruction
irrespective of volatile semantics. The fence instruction guarantees that
accesses before the fence will complete before the accesses comin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63375
--- Comment #16 from Pranith Kumar ---
This is not a good use case(it is a bit twisted, invalid too maybe?), but when
I try to read the stack without aliasing, the volatile write which I performed
is not visible.
#include
#include
#include
t
-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: bobby.prani at gmail dot com
A read within the region of code enclosed by barriers is being moved out of the
regions. Test case follows:
#include
typedef struct {
int counter;
} atomic_t;
static inline int atomic_read
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63375
Pranith Kumar changed:
What|Removed |Added
CC||bobby.prani at gmail dot com
++
Assignee: unassigned at gcc dot gnu.org
Reporter: bobby.prani at gmail dot com
Created attachment 33641
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33641&action=edit
pre-processed file
The compilation of the attached pre-processed file takes 2.5G memory. Not
exactly a reg
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63444
--- Comment #1 from Pranith Kumar ---
Just FYI, clang compiles the same file using 1G memory.
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: bobby.prani at gmail dot com
Target Milestone: ---
Consider:
typedef void (*obj_t)(void);
class parent {
public:
struct obj_base
16 matches
Mail list logo
