[Bug target/83748] Local variables not aligned to word boundary

2018-04-26 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83748 --- Comment #10 from Sumit --- (In reply to Segher Boessenkool from comment #9) Thanks Segher for your comment. I have gone through the changes and seems like they are relevant to "volatile bitfield". Just wanted to confirm (double check) if the

[Bug target/83748] Local variables not aligned to word boundary

2018-04-25 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83748 --- Comment #8 from Sumit --- Hi Segher, I somehow missed the below update from your side. Can you help me understand if this was some known issue in GCC which got fixed in r205896? If yes, can you let us know if got fixed in 4.8.1 version? Th

[Bug c/84054] New: seems -fno-bounds-checking no longer supported

2018-01-25 Thread sbansal at ciena dot com
Assignee: unassigned at gcc dot gnu.org Reporter: sbansal at ciena dot com Target Milestone: --- Hi, We are migrating from 3.4.5 to 4.8.1 compiler and some of our code is using "-fno-bounds-checking" option to avoid doing bounds check on a special piece of code.

[Bug target/83748] Local variables not aligned to word boundary

2018-01-10 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83748 --- Comment #6 from Sumit --- mstrict-align does not seems to help. Only aligning them forcefully does work. ome_CardCfgPxfp_t xfpPecInfo __attribute__((aligned(4))); ome_CardCfgPsfp_t sfpPecInfo __attribute__

[Bug target/83748] Local variables not aligned to word boundary

2018-01-09 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83748 --- Comment #5 from Sumit --- PACK_SUFFIX_ALWAYS_PACK is defined as __attribute__ ((__packed__)). But each individual element in the structure is of 4 bytes. I understand that 4.8.x is not supported any more but we have progressed our developme

[Bug c/83748] Local variables not aligned to word boundary

2018-01-08 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83748 --- Comment #2 from Sumit --- (In reply to Andrew Pinski from comment #1) > What target is this for? > > Also what type is ome_CardCfgPxfp_t ? The target is powerpc. Structure definition is : typedef PACK_PREFIX_ALWAYS_PACK struct ome_CardCf

[Bug c/83748] New: Local variables not aligned to word boundary

2018-01-08 Thread sbansal at ciena dot com
Assignee: unassigned at gcc dot gnu.org Reporter: sbansal at ciena dot com Target Milestone: --- While migrating from 3.4.5 to 4.8.1 tool chain, seeing issues with unaligned address. The same code did not produce unaligned address in 3.4.5 but in 4.8.1 seeing such an issue

[Bug c/83597] New: Compilation error reg multiple declaration

2017-12-27 Thread sbansal at ciena dot com
Assignee: unassigned at gcc dot gnu.org Reporter: sbansal at ciena dot com Target Milestone: --- While compiling the 4.8.1 tool chain, getting the following error. It would be really appreciated if some one can help us on this. Tool chain is configured like : ../configure

[Bug c/83175] compiler optimizing the code corresponding to double precision operations

2017-11-26 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83175 --- Comment #3 from Sumit --- (In reply to Andrew Pinski from comment #1) > Try -fno-strict-aliasing as it looks like the code is violating C/C++ > aliasing rules. Hi Andrew, It does not have any effect. Still the same problem.

[Bug c/83175] compiler optimizing the code corresponding to double precision operations

2017-11-26 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83175 --- Comment #2 from Sumit --- (In reply to Andrew Pinski from comment #1) > Try -fno-strict-aliasing as it looks like the code is violating C/C++ > aliasing rules. Thanks for the quick response. I am trying that and will let you know.

[Bug c/83175] New: compiler optimizing the code corresponding to double precision operations

2017-11-26 Thread sbansal at ciena dot com
: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: sbansal at ciena dot com Target Milestone: --- I am migrating my tool chain from 3.4.5 to 4.8.1. Migration to 4.8.1 is working great till now but the only problem I am recently

[Bug libstdc++/80340] error: 'write' was not declared in this scope

2017-04-06 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80340 Sumit changed: What|Removed |Added Status|RESOLVED|WAITING Resolution|INVALID

[Bug libstdc++/80340] error: 'write' was not declared in this scope

2017-04-06 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80340 --- Comment #5 from Sumit --- (In reply to Jonathan Wakely from comment #4) > (In reply to Jonathan Wakely from comment #2) > > Configuring GCC with --disable-libstdcxx-verbose will remove the use of > > write in that file Is this flag --disable

[Bug libgcc/80314] Undefined reference to __dso_handle & __cxa_atexit

2017-04-06 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80314 --- Comment #7 from Sumit --- (In reply to Jonathan Wakely from comment #6) > Your configure options include: --enable-__cxa_atexit > > Why are you using that if your system doesn't support it? We are upgrading from 4.3.3 to 4.8.1. We had this

[Bug libstdc++/80340] error: 'write' was not declared in this scope

2017-04-06 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80340 --- Comment #3 from Sumit --- ../gcc-4.8/configure LDFLAGS="-L/opt/sp2/lib" --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=powerpc-wrs-vxworks --disable-libmudflap --disable-libssp --disable-libstdc

[Bug libstdc++/80340] New: error: 'write' was not declared in this scope

2017-04-06 Thread sbansal at ciena dot com
Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: sbansal at ciena dot com Target Milestone: --- While building GCC, I am seeing below error : ../../../../gcc-4.8/libstdc++-v3/libsupc++/pure.cc: In function 'void __cxxabiv1::__cxa_pure_virtual()':

[Bug libgcc/80319] New: Support for floatundidf and floatundisf

2017-04-04 Thread sbansal at ciena dot com
Assignee: unassigned at gcc dot gnu.org Reporter: sbansal at ciena dot com Target Milestone: --- While migrating to a newer tool chain, corresponding to float and double data types, __floatundisf and __floatundidf are being generated in assembly respectively. Checking the GCC

[Bug libgcc/80314] Undefined reference to __dso_handle & __cxa_atexit

2017-04-04 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80314 --- Comment #3 from Sumit --- (In reply to Jonathan Wakely from comment #1) > I think these both need to come from either libc or libgcc. Is it something that I have missed while compiling the tool chain? Please suggest.

[Bug libgcc/80314] Undefined reference to __dso_handle & __cxa_atexit

2017-04-04 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80314 --- Comment #2 from Sumit --- (In reply to Jonathan Wakely from comment #1) > I think these both need to come from either libc or libgcc. I have checked my libgcc and it does not have that either. onx-sbansal-01|

[Bug c++/80314] New: Undefined reference to __dso_handle & __cxa_atexit

2017-04-04 Thread sbansal at ciena dot com
: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: sbansal at ciena dot com Target Milestone: --- I am seeing undefined reference to __dso_handle and __cxa_texit during linking stage. BinUtils version : 2.23.52.20130219 What could be the possible problem? hax-dgera-1|

[Bug c++/80247] 'nullptr' was not declared in this scope

2017-03-29 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80247 --- Comment #8 from Sumit --- (In reply to Markus Trippelsdorf from comment #7) > (In reply to Sumit from comment #6) > > Actually, once I have -std=c++11 included in CPPFLAGS, I am able to get rid > > of nullptr problem. > > > > But still in th

[Bug c++/80247] 'nullptr' was not declared in this scope

2017-03-29 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80247 Sumit changed: What|Removed |Added Status|RESOLVED|WAITING Resolution|INVALID

[Bug c++/80247] 'nullptr' was not declared in this scope

2017-03-29 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80247 --- Comment #4 from Sumit --- (In reply to Jonathan Wakely from comment #2) > (In reply to Sumit from comment #0) > > I am migrating my code from 3.4.5 to 4.8.1 and enabled c++11 using > > Why would you choose 4.8.1 and not 4.8.5 ? There are lot

[Bug c++/80247] 'nullptr' was not declared in this scope

2017-03-29 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80247 --- Comment #3 from Sumit --- (In reply to Richard Biener from comment #1) > Provide a testcase. It works for me. Testcase: > > void *p = nullptr; > > > g++-4.8 t.C -S -std=c++11 > > Note that GCC 4.8 is no longer maintained, please use at l

[Bug c++/80247] New: 'nullptr' was not declared in this scope

2017-03-28 Thread sbansal at ciena dot com
mponent: c++ Assignee: unassigned at gcc dot gnu.org Reporter: sbansal at ciena dot com Target Milestone: --- I am migrating my code from 3.4.5 to 4.8.1 and enabled c++11 using -std=C++11 but I am getting below error : In file included from /vobs/optnet_comms/comms_application

[Bug preprocessor/80231] Error missing binary operator before token "("

2017-03-27 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80231 --- Comment #2 from Sumit --- (In reply to Andrew Pinski from comment #1) > Looks like a dup of bug 36453. Hi Andrew, yes I did check that and modified the code like below : #elif (LINUX || ME_BSD_LIKE) && defined(KERNEL_VERSION) && (LINUX

[Bug preprocessor/80231] New: Error missing binary operator before token "("

2017-03-27 Thread sbansal at ciena dot com
Component: preprocessor Assignee: unassigned at gcc dot gnu.org Reporter: sbansal at ciena dot com Target Milestone: --- My product is being migrating from GCC 4.4.1 to 4.8.1 and while compiling the existing code with newer tool chain, I am seeing below error : In file inc

[Bug libstdc++/79862] Compilation error while building libstdc++

2017-03-07 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79862 Sumit changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug libstdc++/79862] Compilation error while building libstdc++

2017-03-06 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79862 --- Comment #6 from Sumit --- Hi Andrew, Somehow these files were missing in my package. I have recopied them back and things have moved further. Now, I am seeing compilation error at : ../../../../../gcc-4.8/libstdc++-v3/src/c++11/debug.cc -o

[Bug libstdc++/79862] Compilation error while building libstdc++

2017-03-06 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79862 --- Comment #5 from Sumit --- (In reply to Sumit from comment #4) > (In reply to Andrew Pinski from comment #3) > > --disable-hosted-libstdcxx \ > > > > That is more likely the cause. non-hosted libstdc++ is not well tested. > Hi Andr

[Bug libstdc++/79862] Compilation error while building libstdc++

2017-03-06 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79862 --- Comment #4 from Sumit --- (In reply to Andrew Pinski from comment #3) > --disable-hosted-libstdcxx \ > > That is more likely the cause. non-hosted libstdc++ is not well tested. Hi Andrew, Thanks for the comments. Actually, when

[Bug libstdc++/79862] Compilation error while building libstdc++

2017-03-06 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79862 --- Comment #2 from Sumit --- (In reply to Richard Biener from comment #1) > Note GCC 4.8.1 is no longer maintained. Hi Richard, I understand that 4.8.1 is no longer supported. Actually, our project in current state can't move to any version be

[Bug c++/79862] New: Compilation error while building libstdc++

2017-03-04 Thread sbansal at ciena dot com
++ Assignee: unassigned at gcc dot gnu.org Reporter: sbansal at ciena dot com Target Milestone: --- Dear Team, I am trying to build 4.8.1 libstdc++-v3 library and I am seeing some compilation errors. Please help. Also, I was able to compile libgcc successfully. GCC

[Bug target/79623] error building a cross compiler for powerpc

2017-02-22 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79623 --- Comment #6 from Sumit --- Hi Richard, Do you have any more suggestion for me? Regards, Sumit

[Bug target/79623] error building a cross compiler for powerpc

2017-02-21 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79623 --- Comment #5 from Sumit --- Below error log indicates that the C standard library headers are found in /usr/include. Isn't? In file included from /usr/include/stdlib.h:314:0, from ../../gcc-4.8/libiberty/regex.c:130: /usr/incl

[Bug target/79623] error building a cross compiler for powerpc

2017-02-20 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79623 --- Comment #3 from Sumit --- Hi Richard, I think this could be the root cause. checking for intptr_t... no checking for uintptr_t... no checking for ssize_t... no checking for pid_t... no Could you please help me understanding this behaviour

[Bug target/79623] error building a cross compiler for powerpc

2017-02-20 Thread sbansal at ciena dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79623 --- Comment #2 from Sumit --- Thanks Richard for the quick response. I understand your point but actually it has been decided to be at 4.8.1 as far as our current project is concerned. Is it possible for you to at least give me some pointers wh

[Bug target/79623] New: error building a cross compiler for powerpc

2017-02-19 Thread sbansal at ciena dot com
: target Assignee: unassigned at gcc dot gnu.org Reporter: sbansal at ciena dot com Target Milestone: --- Created attachment 40778 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40778&action=edit config.log GCC version being compiled : 4.8.1 Host machine GCC version

[Bug c/79573] New: binutils make install fails

2017-02-17 Thread sbansal at ciena dot com
: unassigned at gcc dot gnu.org Reporter: sbansal at ciena dot com Target Milestone: --- Host machine gcc version : -bash-4.2$ gcc -v Using built-in specs. COLLECT_GCC=/usr/bin/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.5/lto