BTW, one thing I noticed is that the "error code" field in the
std::system_error exception which is raised, seems to be set to EPERM
("Operation not permitted"), but this code is not apparently caused by a
system call (determined by stracing the process).
For instance, changing the test case to th
Package: libstdc++6
Version: 4.5-20100227-1
Severity: normal
File: libstdc++
The following program:
#include
#include
int g = 0;
void f ()
{
g++;
}
int main ()
{
std::thread t (f);
t.join ();
std::cout << "after joing, g = " << g << std::endl;
return 0;
--- Comment #7 from kargl at gcc dot gnu dot org 2010-04-04 20:28 ---
(In reply to comment #5)
> (In reply to comment #1)
> > > should -c explain how a .mod file is created?
> >
> > IMHO, the answer is a resounding 'no.' Adding such information
> > would simply add unneeded clutter to
LAST_UPDATED: Obtained from SVN: tags/gcc_4_4_3_release revision 156151
Target: i486-linux-gnu
gcc version 4.4.3 (Debian 4.4.3-6)
Native configuration is i486-pc-linux-gnu
=== g++ tests ===
Running target unix
UNRESOLVED: attribute_plugin.c compilation, -I.
-I/build/buildd-gcc
Accepted:
cloog-ppl_0.15.9-1.diff.gz
to main/c/cloog-ppl/cloog-ppl_0.15.9-1.diff.gz
cloog-ppl_0.15.9-1.dsc
to main/c/cloog-ppl/cloog-ppl_0.15.9-1.dsc
cloog-ppl_0.15.9.orig.tar.gz
to main/c/cloog-ppl/cloog-ppl_0.15.9.orig.tar.gz
libcloog-ppl-dev_0.15.9-1_amd64.deb
to main/c/cloog-ppl/libc
cloog-ppl_0.15.9-1_amd64.changes uploaded successfully to localhost
along with the files:
cloog-ppl_0.15.9-1.dsc
cloog-ppl_0.15.9.orig.tar.gz
cloog-ppl_0.15.9-1.diff.gz
libcloog-ppl-dev_0.15.9-1_amd64.deb
libcloog-ppl0_0.15.9-1_amd64.deb
Greetings,
Your Debian queue daemon (runn
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2010-04-04 15:02
---
That idea of a --clean is interesting. I can see where it would be useful to
force a recompile of module files. I am not sure what the actual flag should
be. Of course one could use make to do all of this.
--
On 04.04.2010 11:36, Santiago Vila wrote:
Hello.
Latest m4 FTBFS on several architectures, for different reasons.
On hppa, it seems to trigger a gcc bug:
gcc -std=gnu99 -g -Wall -O2 -o test-fpurge test-fpurge.o libtests.a
../lib/libm4.a libtests.a
collect2: malloc.c:3096: sYSMALLOc: Assert
Hello.
Latest m4 FTBFS on several architectures, for different reasons.
On hppa, it seems to trigger a gcc bug:
gcc -std=gnu99 -g -Wall -O2 -o test-fpurge test-fpurge.o libtests.a
../lib/libm4.a libtests.a
collect2: malloc.c:3096: sYSMALLOc: Assertion `(old_top == (((mbinptr) (((char
*) &
--- Comment #5 from rwild at gcc dot gnu dot org 2010-04-04 08:40 ---
(In reply to comment #1)
> > should -c explain how a .mod file is created?
>
> IMHO, the answer is a resounding 'no.' Adding such information
> would simply add unneeded clutter to the manual, and should be
> an insu
There are disparities between your recently accepted upload and the
override file for the following file(s):
lib32gcc1_4.4.3-7_amd64.deb: package says priority is optional, override says
extra.
Please note that a list of new sections were recently added to the
archive: cli-mono, database, debug
Accepted:
cpp-4.4_4.4.3-7_amd64.deb
to main/g/gcc-4.4/cpp-4.4_4.4.3-7_amd64.deb
fixincludes_4.4.3-7_amd64.deb
to main/g/gcc-4.4/fixincludes_4.4.3-7_amd64.deb
g++-4.4-multilib_4.4.3-7_amd64.deb
to main/g/gcc-4.4/g++-4.4-multilib_4.4.3-7_amd64.deb
g++-4.4_4.4.3-7_amd64.deb
to main/g/gcc-4.
12 matches
Mail list logo
