After purging the package libpthread-dev the above code doesn't make g++ yield
that error message. The program actually works like it's supposed to after
being compiled.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection a
--- Comment #7 from whaley at cs dot utsa dot edu 2006-12-19 00:31 ---
>Depends on what you mean by fixable by the programmer because most people don't
know anything about precusion issues.
Most people don't know programming at all, so I guess you are suggesting that
errors that are f
That version of binutils is nowhere to be found in Debian: not in
testing, not in unstable and not in experimental. So I'm wondering
why it is necessary to build-depend on it, and whether or not I should
revert that particular change (see revision 1669).
I'm already building with BINUTILSV set to
Ludovic Brenta wrote:
> Kevin Brown writes:
> > That may be true, but developers aren't the only ones who might make
> > use of these files. Anyone who gets a crash in an Ada application
> > could get a much better traceback (for filing a bug report) with
> > these files in place than without.
> >
Ludovic Brenta writes:
> Kevin Brown writes:
> > That may be true, but developers aren't the only ones who might make
> > use of these files. Anyone who gets a crash in an Ada application
> > could get a much better traceback (for filing a bug report) with
> > these files in place than without.
>
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-12-18 23:02 ---
>I cannot, of course, force you to admit it, but 323 is a bug fixable by the
> programmer, and this one is not.
Depends on what you mean by fixable by the programmer because most people don't
know anything about pr
Kevin Brown writes:
> That may be true, but developers aren't the only ones who might make
> use of these files. Anyone who gets a crash in an Ada application
> could get a much better traceback (for filing a bug report) with
> these files in place than without.
>
> Independent of the potential i
--- Comment #5 from whaley at cs dot utsa dot edu 2006-12-18 22:14 ---
I cannot, of course, force you to admit it, but 323 is a bug fixable by the
programmer, and this one is not. The other requires a lot of work in the
compiler, and this does not. So, viewing them as the same can be d
--- Comment #86 from pinskia at gcc dot gnu dot org 2006-12-18 22:04
---
*** Bug 30255 has been marked as a duplicate of this bug. ***
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=323
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-12-18 22:04 ---
The problem with register spilling and what PR 323 is talking about is all the
same issue really, it is just exposed differently.
*** This bug has been marked as a duplicate of 323 ***
--
pinskia at gcc dot gnu
--- Comment #3 from whaley at cs dot utsa dot edu 2006-12-18 21:16 ---
BTW, in case it isn't obvious, here's the fix that I typically use for problems
like bug 323 that I cannot when it is gcc itself that is unpredictably spilling
the computation:
void test(double x, double y)
{
const
--- Comment #2 from whaley at cs dot utsa dot edu 2006-12-18 20:43 ---
Hi,
While it may be decided not to fix this problem, this is not a duplicate of bug
323, and so it should be closed for another reason if you want to ignore it.
323 has a problem because of the function call, where
cpp-4.2-doc_4.2-20061217-1_all.deb
to pool/main/g/gcc-4.2/cpp-4.2-doc_4.2-20061217-1_all.deb
cpp-4.2_4.2-20061217-1_i386.deb
to pool/main/g/gcc-4.2/cpp-4.2_4.2-20061217-1_i386.deb
fixincludes_4.2-20061217-1_i386.deb
to pool/main/g/gcc-4.2/fixincludes_4.2-20061217-1_i386.deb
(new) g++-4.2-mult
Accepted:
gcc-snapshot_20061217-1.diff.gz
to pool/main/g/gcc-snapshot/gcc-snapshot_20061217-1.diff.gz
gcc-snapshot_20061217-1.dsc
to pool/main/g/gcc-snapshot/gcc-snapshot_20061217-1.dsc
gcc-snapshot_20061217-1_i386.deb
to pool/main/g/gcc-snapshot/gcc-snapshot_20061217-1_i386.deb
gcc-snapshot
Ludovic Brenta wrote:
> Hi Kevin,
>
> Thanks for taking all that trouble. The debugging information should
> not go into the package libgnat-4.1, because that's a run-time-only
> package not intended for developers.
That may be true, but developers aren't the only ones who might make
use of thes
--- Comment #85 from pinskia at gcc dot gnu dot org 2006-12-18 20:16
---
*** Bug 30255 has been marked as a duplicate of this bug. ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-18 20:16 ---
*** This bug has been marked as a duplicate of 323 ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
gcc-snapshot_20061217-1_i386.changes uploaded successfully to localhost
along with the files:
gcc-snapshot_20061217-1.dsc
gcc-snapshot_20061217.orig.tar.gz
gcc-snapshot_20061217-1.diff.gz
gcc-snapshot_20061217-1_i386.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, em
gcc-4.2_4.2-20061217-1_i386.changes uploaded successfully to localhost
along with the files:
gcc-4.2_4.2-20061217-1.dsc
gcc-4.2_4.2-20061217.orig.tar.gz
gcc-4.2_4.2-20061217-1.diff.gz
gcc-4.2-source_4.2-20061217-1_all.deb
cpp-4.2-doc_4.2-20061217-1_all.deb
libgcj8-jar_4.2-20061217-1_all
Hi Kevin,
Thanks for taking all that trouble. The debugging information should
not go into the package libgnat-4.1, because that's a run-time-only
package not intended for developers.
Instead, the debugging information should go either to a new package
(libgnat-4.1-dbg), either into package gnat
I wrote:
Having looked a little deeper, it appears it *does* use dh_strip after
all. The file to examine is debian/rules.d/binary-ada.mk.
I'll try modifying that file to add --keep-debug to the dh_strip
commands to see if that does anything useful...
And indeed it does. Very nicely, actua
> On Sat, Dec 16, 2006 at 03:37:48PM +0300, Nikita V. Youshchenko wrote:
> > > - If you have a package that needs updating, *please* don't forget
> > > to contact us. *Don't expect us to find out about it on our own*.
> >
> > Please allow gcc-doc-defaults 4.1.1.nf3 into etch.
> > This upload fi
22 matches
Mail list logo