Matthias Klose wrote:
>
> The -Wconversion option to gcc is documented as doing two things:
>
>
> `-Wconversion'
> Warn if a prototype causes a type conversion that is different
> from what would happen to the same
Segher Boessenkool <[EMAIL PROTECTED]> writes:
> Matthias Klose wrote:
>> It'd be nice if these two behaviors were two controlled via two
>> separate flags. The second behavior would have caught a bug I've been
>> hunting for hours, while the first behavior is very undesirable to me
>> (and useles
Zack Weinberg wrote:
>
> I'm very much in favor of making -Wconversion more useful, but is
> there any reason not to shift the argument-type-conversion warnings
> entirely over to -Wtraditional? Particularly if the warning is
> avoided for prototypes in system headers (so that 'sinf' and the like
Segher Boessenkool <[EMAIL PROTECTED]> writes:
> Zack Weinberg wrote:
>>
>> I'm very much in favor of making -Wconversion more useful, but is
>> there any reason not to shift the argument-type-conversion warnings
>> entirely over to -Wtraditional? Particularly if the warning is
>> avoided for pro
Processing commands for [EMAIL PROTECTED]:
> reassign 160093 gcc-3.2
Bug#160093: conflicting file ownership in libstdc++4 and gcc-3.2-nof
Bug reassigned from package `libstdc++4' to `gcc-3.2'.
> --
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system ad
Your message dated Sun, 29 Dec 2002 12:01:35 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Processed: does this bug still apply?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now y
On Sun, 29 Dec 2002, Zack Weinberg wrote:
> I'm very much in favor of making -Wconversion more useful, but is
> there any reason not to shift the argument-type-conversion warnings
> entirely over to -Wtraditional? Particularly if the warning is
> avoided for prototypes in system headers (so that
Your message dated Sun, 29 Dec 2002 14:27:35 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#138201: cpp: macro expansion inside macro calling
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
../../gnatlink -v gnatpsta -o ../../gnatpsta --GCC="../../xgcc -B../../
-I../rts -I. -I/build/buildd/gcc-snapshot-20021228/src/gcc/ada"\
../targtyps.o deftarg.o ../../prefix.o ../../version.o
../rts/libgnat.a ../../../libiberty/libiberty.a
GNATLINK 3.3 20021228 (prerelea
[ CVS 20021228, same as for the powerpc-linux build ]
../../xgcc -B../../ -c -g -O2 -g -O2 -W -Wall -gnatpg -I.
-I/build/buildd/gcc-snapshot-20021228/src/gcc/ada a-nlcefu.ads
a-ngcefu.adb: In function
`ada.numerics.long_complex_elementary_functions.arccoth':
a-ngcefu.adb:298: error: insn doe
>Submitter-Id: net
>Originator:James Troup <[EMAIL PROTECTED]>
>Organization: The Debian Project
>Confidential: no
>Synopsis:
>Severity: serious
>Priority: medium
>Category:
>Class: ice-on-legal-code
>Release: 3.2.1 (Debian) (Debian unstable)
>Environment
Camm Maguire writes:
> Greetings!
>
> Matthias Klose <[EMAIL PROTECTED]> writes:
>
> > [keeping all the people in the CC]
> >
> > Scanning the reports, I see Matthew Wilcox beeing asked about:
> >
> > > > In either case, I will need a knowledgeable hppa person to advise,
> > > > discuss and hel
>Submitter-Id: net
>Originator:James Troup <[EMAIL PROTECTED]>
>Organization: The Debian Project
>Confidential: no
>Synopsis:
>Severity: serious
>Priority: medium
>Category: target
>Class: ice-on-legal-code
>Release: 3.2.1 (Debian) (Debian unstable)
>Envir
Thank you very much for your problem report.
It has the internal identification `target/9090'.
The individual assigned to look at your
report is: unassigned.
>Category: target
>Responsible:unassigned
>Synopsis: arm ICE with >= -O2; regression from 2.95
>Arrival-Date: Sun Dec 29
Package: libstdc++5
Version: 1:3.2.1-0pre3
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
bohr:/home/anthony# apt-get build-dep libstdc++5=1:3.2.1-0pre3
Reading Package Lists... Done
Building Dependency Tree... Done
E: Unable to find a source package for libstdc++5
bohr:/home/ant
>Submitter-Id: net
>Originator:Bill Allombert <[EMAIL PROTECTED]>
>Organization: The Debian Project
>Confidential: no
>Synopsis:
>Severity: non-critical
>Priority: low
>Category: c
>Class: change-request
>Release: 3.2.1 (Debian) (Debian unstable)
>Environm
On Sat, 28 Dec 2002, Matthias Klose wrote:
> ffi_type_uint8 and other arguments shorter than one word are
> not passed in correctly to the function called by ffi_call.
For an ffi_type_uint8, ffi_call expects the corresponding value
pointer to be a (unsigned char *). So this is correct usage:
Processing commands for [EMAIL PROTECTED]:
> forwarded 168086 [EMAIL PROTECTED]
Bug#168086: g++-3.2: arm ICE with >= -O2; regression from 2.95
Noted your statement that Bug has been forwarded to [EMAIL PROTECTED]
> retitle 168086 [PR target/9090] arm ICE with >= -O2; regression from 2.95
Bug#1680
>Category: ada
>Synopsis: [3.3 branch regression] Ada bootstrap failure on powerpc-linux
>Confidential: no
>Severity: serious
>Priority: medium
>Class: sw-bug
>Submitter-Id: net
>Originator: [EMAIL PROTECTED]
>Release:gcc-3_3-branch 20021228
>Environ
>Category: ada
>Synopsis: [3.3 branch] Ada bootstrap failure on mipsel-linux
>Confidential: no
>Severity: critical
>Priority: medium
>Class: sw-bug
>Submitter-Id: net
>Originator: [EMAIL PROTECTED]
>Release:gcc-3_3-branch 20021228
>Environment:
mipse
>Category: bootstrap
>Synopsis: [3.3 branch regression] bootstrap failures on m68k-linux
>Confidential: no
>Severity: critical
>Priority: medium
>Class: sw-bug
>Submitter-Id: net
>Originator: [EMAIL PROTECTED]
>Release:gcc-3_3-branch CVS 20021228
>En
>Category: bootstrap
>Synopsis: [3.3 branch regression] bootstrap failures on arm-linux
>Confidential: no
>Severity: critical
>Priority: medium
>Class: sw-bug
>Submitter-Id: net
>Originator: [EMAIL PROTECTED]
>Release:gcc-3_3-branch 20021228
>Environ
> Matthias Klose writes:
Matthias> ../targtyps.o(.text+0x6a): In function `get_target_long_double_size':
Matthias> : undefined reference to `rs6000_long_double_type_size'
Matthias> ../targtyps.o(.text+0x6e): In function `get_target_long_double_size':
Matthias> : undefined reference to `rs6000_
Your message dated Sun, 29 Dec 2002 17:05:51 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#174626: libstdc++5: Source seems to have disappeared...
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Synopsis: libffi: problems with uint8 on powerpc
Responsible-Changed-From-To: unassigned->jsturm
Responsible-Changed-By: jsturm
Responsible-Changed-When: Sun Dec 29 08:13:07 2002
Responsible-Changed-Why:
I'll handle it.
State-Changed-From-To: open->feedback
State-Changed-By: jsturm
State-Chang
Synopsis: arm ICE with >= -O2; regression from 2.95
State-Changed-From-To: open->closed
State-Changed-By: lerdsuwa
State-Changed-When: Sun Dec 29 10:04:39 2002
State-Changed-Why:
PR9090 contains a complete testcase, which is missing from this bug report.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl
David Edelsohn writes:
> > Matthias Klose writes:
>
> Matthias> ../targtyps.o(.text+0x6a): In function
> `get_target_long_double_size':
> Matthias> : undefined reference to `rs6000_long_double_type_size'
> Matthias> ../targtyps.o(.text+0x6e): In function
> `get_target_long_double_size':
> Ma
Matthias Klose writes:
> David Edelsohn writes:
> > > Matthias Klose writes:
> >
> > Matthias> ../targtyps.o(.text+0x6a): In function
> > `get_target_long_double_size':
> > Matthias> : undefined reference to `rs6000_long_double_type_size'
> > Matthias> ../targtyps.o(.text+0x6e): In function
> Matthias Klose writes:
Matthias> ok, found. should this be applied to the 3.3 branch again?
Matthias> 2002-04-02 David Edelsohn <[EMAIL PROTECTED]>
Matthias> * config/rs6000/rs6000.h (WIDEST_HARDWARE_FP_SIZE): Define.
Maybe. Or maybe it should be defined identically to
LIBGCC2_
29 matches
Mail list logo
