On GNU/Linux, you need to use -pthread or -D_REENTRANT at compilation
time, and you need to use -pthread or -lpthread at link time.
? gcc mailing list certainly worth reading for users. I always thought
that -lpthread at link time is enough.
Alexey
On 4/17/10, Alan Lehotsky qsm...@earthlink.net wrote:
Take a look at the at(1) or batch(1) commands if you really want to execute
a command and logout while it's still running.
Or screen(1)
On Tue, Mar 16, 2010 at 9:05 PM, Tristan Gingold ging...@adacore.com wrote:
On Mar 16, 2010, at 3:50 PM, H.J. Lu wrote:
2010/3/8 Paweł Sikora pl...@agmk.net:
hi,
during development a cross platform appliacation on x86 workstation
i've enabled an alignemnt checking [1] to catch possible
On Tue, Mar 16, 2010 at 9:48 PM, Tristan Gingold ging...@adacore.com wrote:
On Mar 16, 2010, at 4:37 PM, Alexey Salmin wrote:
I am interested in an -mstrict-alignment option for x86.
Not sure it will be useful. The libc still does unaligned accesses IIRC.
Wow. What for?
Well, simply
On Tue, Mar 9, 2010 at 3:58 PM, Basile Starynkevitch
bas...@starynkevitch.net wrote:
Hello All,
With a recently compiled gcc-trunk on x86-64/linux, I am compiling the
folllowing example:
#
/* file testmanychar.c */
extern void g (int, char *, char *, char *);
void
f
There's another funny thing about gcc3 behavior which I've just discovered:
$ gcc -v 21 | grep version
gcc version 3.4.2
$ gcc -o mem mem.c ; ./mem
-1024
$ gcc -o mem1 mem1.c ; ./mem1
0
$ cat mem.c
#include stdio.h
int main() {
char *p1, *p2;
{
char a[1024];
2008/12/16 Dennis Clarke dcla...@blastwave.org:
Hi,
The following program segfaults when compiled with gcc
but runs fine when compiled with g++ or icc (the intel C compiler)
#include stdio.h
struct Hello {
char world[20];
};
struct Hello s(){
struct Hello r;
2008/11/20 Michael Matz [EMAIL PROTECTED]:
Hi,
On Wed, 19 Nov 2008, H.J. Lu wrote:
On Wed, Nov 19, 2008 at 7:18 PM, Nicholas Nethercote
[EMAIL PROTECTED] wrote:
On Tue, 18 Nov 2008, H.J. Lu wrote:
I used malloc to create my arrays instead of creating the in the stack.
My program is
There are issues of Garbage Collection from libgcc or Boehms's GC
that you possibly can't use another allocators that these defaults,
unless you have control of the manager of the whole memory,
and it's too complex due to the gigant size of the project.
[EMAIL PROTECTED]:~/gcc/src/include$
Hello, here's my application. Please, leave your comments as I still
have two days to fix it if something is wrong :)
Project
I want to make some improvements in the Lexer/cpplib area:
1) Change the way of file handling
-- Mmap file into memory if possible instead of allocating a buffer
(if no
or something but have not found anything.
So I want to ask: what's wrong with XDELETEVEC (and XDELETE as well)?
Alexey Salmin
sometimes with this task.
Alexey Salmin
12 matches
Mail list logo
