22 May 2013 10:25
22 May 2013 02:54
How to use AddressSanitizer of gcc-4.8 on Arm target
Jungsoo Son <jungsoo.son <at> lge.com>
2013-05-22 00:54:27 GMT
2013-05-22 00:54:27 GMT
AddressSanitizer of Gcc-4.8 is not available on Arm arch yet. I have found it in gcc-4.8 release note. But, I want to try to use asan on arm target. In my case, when I compiled a sample with fsanitizer=address option I have faced the following warning message. And Asan did not detect memory error. I think it does not work on the arm target. Is there any way to test AddressSanitizer on arm through changing compile option or enable some-feature? $ arm-none-linux-gnueabi-gcc -fsanitize=address -fno-omit-frame-pointer -g -o test use-after-free.c use-after-free.c:1:0: warning: -fsanitize=address not supported for this target [enabled by default] #include <stdlib.h> ^ regards, Jungsoo
19 May 2013 21:53
Fwd: Problem calling C .dll library from Fortran using ISO_C_BINDING
Pietro Ghillani <ghillo.p <at> gmail.com>
2013-05-19 19:53:43 GMT
2013-05-19 19:53:43 GMT
Hi everyone! I am writing Fortran code on Windows 7 32-bit with MinGW. I am using the Fortran 2003 feature that allows to access APIs contained in a third party .dll library (probably) written in C with some success as I have been able to call an initialization function and a function that returns the library version. The problems come when I try to call a function to create a new file that requires three arguments: a file ID, the path to the file including its name and the path to a folder to store the temporary files. The documentation defines the syntax of the function as follows: long NewFile(long fID, char* Filename, char* Path) In Fortran I have created an interface: INTERFACE FUNCTION NewFile(uID,FileName,Path) BIND(C, NAME='NewFile') USE, INTRINSIC :: ISO_C_BINDING, ONLY: C_CHAR, C_LONG IMPLICIT NONE INTEGER(C_LONG) :: NewFile INTEGER(C_LONG), VALUE :: fID CHARACTER(C_CHAR) :: Filename(*) CHARACTER(C_CHAR) :: Path(*) END FUNCTION END INTERFACE Then I call the function with:(Continue reading)
18 May 2013 14:05
Fwd: Method call and calling convention
Kifa The Great <kifathegreat <at> gmail.com>
2013-05-18 12:05:09 GMT
2013-05-18 12:05:09 GMT
Hello!
I have faced a problem using GDB with GCC 4.8.0 x86 on Windows XP and
Ubuntu 12.04. Here is the issue description.
GDB has commands to call function from the program being debugged.
They are print and call. But unfortunately the mentioned above
commands work incorrectly for class methods with __thiscall calling
convention. Windows x86 targets are using the __thiscall calling
convention for C++ class-member functions by default from GCC 4.7.
Judging by command return values GDB does not set object address (this
pointer) to ECX registry before method call. So these commands trigger
for some object only if last executed line of the program being
debugged contains method call for the same object. In this case ECX
registry will contain necessary address (this pointer). For methods
with __cdecl calling convention print (call) works perfectly.
Could you please tell me if this is a bug, feature or maybe I do
something wrong?
Thanks,
Petr
C++ program Test:
01: #include <iostream>
02: class Test
03: {
04: public:
05: Test(int value) : _value(value) {}
06: int value() const __attribute__((thiscall)) { return _value; }
(Continue reading)
17 May 2013 14:47
17 May 2013 14:33
Re: SVN checkout failure
Csaba Raduly <rcsaba <at> gmail.com>
2013-05-17 12:33:05 GMT
2013-05-17 12:33:05 GMT
On Thu, May 16, 2013 at 2:16 PM, Alec Teal <a.teal <at> warwick.ac.uk> wrote: > I did the same thing yesterday, it's > svn checkout svn://gcc.gnu.org/svn/gcc/trunk ./sources > NOT http! Good for you, but I'm behind seven proxies; I have to use http :( http://xmodulo.com/2012/12/how-to-use-svn-behind-proxy.html Csaba -- -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds
16 May 2013 14:53
Need to know the reason why GCC able to compile
naveen yadav <yad.naveen <at> gmail.com>
2013-05-16 12:53:25 GMT
2013-05-16 12:53:25 GMT
Dear All,
I am checking below code on gcc 4.4 and gcc 4.6
Below Code compile well.
#include<stdio.h>
int main()
{
struct a{
int c;
int b[];
} d;
return 0;
}
Fail:
#include<stdio.h>
int main()
{
struct a{
int b[];
int c;
} d;
return 0;
}
test.c: In function âmainâ:
test.c:5: error: flexible array member not at end of struct
(Continue reading)
16 May 2013 11:50
SVN checkout failure
Csaba Raduly <rcsaba <at> gmail.com>
2013-05-16 09:50:56 GMT
2013-05-16 09:50:56 GMT
Hi all, I'm trying to download and build GCC, but the checkout fails with: $ svn checkout http://gcc.gnu.org/svn/gcc/trunk sources svn: access to '/svn/gcc/!svn/ver/184997/trunk/zlib/contrib/masmx64/bld_ml64.bat' forbidden What's going on? Csaba Please CC me, I'm nor on the list. -- -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds
16 May 2013 10:38
Request
fomengia glen <gfomengia <at> yahoo.co.uk>
2013-05-16 08:38:18 GMT
2013-05-16 08:38:18 GMT
Dear GCC members, I am a first tme user of GCC. I would like to know which version and how to install it on my sytem. I am using Fedora 18x 86_64 and my pc is an Intel pentium p6200, dual core, 4GB ram memory and 64 bit operating system. Glen
16 May 2013 09:38
Potentially bogus warning about anonymous types
Nathan Ridge <zeratul976 <at> hotmail.com>
2013-05-16 07:38:08 GMT
2013-05-16 07:38:08 GMT
Hello, A while ago I encountered what I believed to be a bogus warning of the form "... uses the anonymous namespace" with GCC 4.8. I posted http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54060 , and I was told there that: 1. The warning is meant to say "... uses an anonymous type" rather than "... uses the anonymous namespace". 2. Aside from the poor wording, the warning is not bogus because it points out a potential ODR violation. I recently encountered the same warning in a different situation, but I don't see where the potential ODR violation is this time. I suspect there may not be one (and thus the warning really is bogus in this case), but I wanted to double-check before filing a bug. Here is the code in question: test.cpp: #include "test.hpp" test.hpp: template <typename T> struct base {(Continue reading)
16 May 2013 01:18
gcc trunk bootstrap fails on darwin with linker assertion
Dara Hazeghi <dhazeghi <at> yahoo.com>
2013-05-15 23:18:27 GMT
2013-05-15 23:18:27 GMT
I've seen this problem on and off several times now (including with the 4.8.0 release). Bootstrap fails linking xgcc in stage 2 with a linker assertion: ld: Assertion failed: (cfiStartsArray[i] != cfiStartsArray[i-1]), function parse, file /SourceCache/ld64/ld64-136/src/ld/parsers/macho_relocatable_file.cpp, line 1555. System is running MacOS X 10.8.3 with Xcode 4.6.1. Has anybody else seen this error? Unfortunately it comes and goes seemingly at random. Thanks, Dara $ ../gcc-trunk/configure --enable-languages=c,c++,objc,obj-c++,fortran,lto --disable-checking --with-gmp=/usr/local/gcc-trunk --with-mpfr=/usr/local/gcc-trunk --with-mpc=/usr/local/gcc-trunk --with-cloog=/usr/local/gcc-trunk --prefix=/usr/local/gcc-trunk $ make -j2 bootstrap ... /Users/dara/Downloads/objdir/./prev-gcc/xg++ -B/Users/dara/Downloads/objdir/./prev-gcc/ -B/usr/local/gcc-trunk/x86_64-apple-darwin12.3.0/bin/ -nostdinc++ -B/Users/dara/Downloads/objdir/prev-x86_64-apple-darwin12.3.0/libstdc++-v3/src/.libs -B/Users/dara/Downloads/objdir/prev-x86_64-apple-darwin12.3.0/libstdc++-v3/libsupc++/.libs(Continue reading)
RSS Feed