Hi,
...
`-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead.
evp_pkey.c: In function 'EVP_PKEY2PKCS8_broken':
evp_pkey.c:382: warning: function called through a non-compatible type
evp_pkey.c:382: note: if this code is reached, the program will abort
evp_pkey.c: In function
--- Comment #1 from happyarch at gmail dot com 2007-01-26 09:54 ---
Created an attachment (id=12958)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12958action=view)
preprocessed sources and output
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30596
--- Comment #1 from dfranke at gcc dot gnu dot org 2007-01-26 09:58 ---
Here, the default value is not documented; it can be found in
3 Environment Variables (If undefined, dynamic adjustment is disabled
by default.), but this is not obvious. Especially, since the omp_get_*
--- Comment #2 from rguenth at gcc dot gnu dot org 2007-01-26 10:55 ---
How did you invoke gcc?
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from burnus at gcc dot gnu dot org 2007-01-26 11:06 ---
And OMP_NUM_THREADS's default setting is completely undefined; does it
use by default one or the maximal number of available processors?
Section 3.3 states:
If undefined one thread per CPU online is used.
--- Comment #2 from jakub at gcc dot gnu dot org 2007-01-26 12:34 ---
The only other place that generates info files is gcc subdir and there it uses
BUILD_INFO conditional, if makeinfo is not present or is too old, it simply
doesn't build the documentation. Perhaps libgomp could do the
--- Comment #12 from bkoz at gcc dot gnu dot org 2007-01-26 12:44 ---
Reopen..
--
bkoz at gcc dot gnu dot org changed:
What|Removed |Added
Status|RESOLVED
--- Comment #3 from manu at gcc dot gnu dot org 2007-01-26 12:57 ---
This should be warned by -Wsequence-points.
--
manu at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #12 from manu at gcc dot gnu dot org 2007-01-26 13:01 ---
(In reply to comment #11)
Subject: Re: Request for -Wundefined
manu at gcc dot gnu dot org [EMAIL PROTECTED] writes:
| Not sure about this one either, there seems to be a warning in C++
| but I am not sure
--- Comment #3 from fxcoudert at gcc dot gnu dot org 2007-01-26 13:07
---
(In reply to comment #2)
The only other place that generates info files is gcc subdir and there it uses
BUILD_INFO conditional, if makeinfo is not present or is too old, it simply
doesn't build the
--- Comment #6 from fxcoudert at gcc dot gnu dot org 2007-01-26 13:11
---
So maybe a right fixinclude change could be to look into _mingw.h for
#define __CRT_INLINE extern __inline__
and change it (for mainline) to
# if __STDC_VERSION__ = 199901L
# define __CRT_INLINE extern inline
--- Comment #2 from fxcoudert at gcc dot gnu dot org 2007-01-26 13:16
---
Created an attachment (id=12960)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12960action=view)
Preprocessed source for file a.c
Minimal testcase using the xgcc binary made before the bootstrap fails:
$
--- Comment #3 from fxcoudert at gcc dot gnu dot org 2007-01-26 13:17
---
Created an attachment (id=12961)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12961action=view)
Preprocessed source file for b.i
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30058
--- Comment #13 from bkoz at gcc dot gnu dot org 2007-01-26 13:23 ---
Revert.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28125
--- Comment #7 from jakub at gcc dot gnu dot org 2007-01-26 13:32 ---
Static linking with -lpthread (which -fopenmp uses) is not supported in
glibc/NPTL. You can probably make it working by adding
-Wl,--whole-archive -lpthread -Wl,--no-whole-archive
to the command line, but there are
--- Comment #3 from rguenth at gcc dot gnu dot org 2007-01-26 13:44 ---
Another thing we should be able to do is combine bit-tests like
if (a (1 b))
if (a (1 c))
...
to a single test
if (a ((1 b) | (1 c)) == ((1 b) | (1 c)))
...
--
--- Comment #4 from jakub at gcc dot gnu dot org 2007-01-26 13:47 ---
As a workaround, gcc could check for this in configure and if it detects the
bug,
override TARGET_ASM_SELECT_SECTION such that on Solaris with this bug
detected it would:
section *
solaris_elf_select_section (tree
--- Comment #14 from bkoz at gcc dot gnu dot org 2007-01-26 13:49 ---
Subject: Bug 28125
Author: bkoz
Date: Fri Jan 26 13:49:42 2007
New Revision: 121203
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121203
Log:
2007-01-26 Benjamin Kosnik [EMAIL PROTECTED]
Revert.
--- Comment #1 from jakub at gcc dot gnu dot org 2007-01-26 13:52 ---
This looks as a very convoluted API, far better would be simply write special
.eh_frame info for the libgomp thread body function which would point the
debuggers/profilers to the stack/saved registers of the thread
We discovered this issue while importing newer gcc 4.1* into NetBSD tree and
saw that suddently it no longer thinks COMDAT is supported.
I've tracked it down to the following change:
http://gcc.gnu.org/viewcvs?view=revrevision=99395
that changed configure.ac to check $ld_date to decide if
--- Comment #1 from uwe at netbsd dot org 2007-01-26 14:18 ---
On the second thought, I might be confused here. Please, leave UNCONFIRMED.
I'll do more testing and get back with an update later today. Sorry.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30598
--- Comment #4 from schnetter at aei dot mpg dot de 2007-01-26 14:36
---
I have read the documentation, and I understand what the option does. I
compile my complete programme and all its libraries with this option.
It was my assumption that the compiler would create working code with
--- Comment #2 from temp at pathengine dot com 2007-01-26 14:42 ---
Can we do anything to work around this issue?
Is there an option, for example, to turn off just named return value
optimisation? (I did a quick search of the manual but couldn't find anything.)
--
--- Comment #2 from manu at gcc dot gnu dot org 2007-01-26 15:34 ---
So what is the correct solution? Use inform or notice? Or don't show the
message as C++ does?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24577
--- Comment #6 from manu at gcc dot gnu dot org 2007-01-26 16:00 ---
OK. I see now. This seems hard to fix, since it is exposing the current
implementation of a conversion to bool.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8715
--- Comment #5 from manu at gcc dot gnu dot org 2007-01-26 16:08 ---
Gabriel, if you could do a quick and dirty list of what remains to be done,
perhaps some potential contributor would try to implement it as an entry point
to GCC development.
--
manu at gcc dot gnu dot org changed:
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-01-26 16:11
---
I understand Erik's concern. -malign-double makes a significant performance
difference on some of these machines and is commonly used.
The surest way to handle this is to put compute intensive code in separate
Hi,
Since bug 30255 has been declared as never going to be fixed, I've been
enjoying going through half a million lines of code looking for places where I
have to declare things long double to keep gcc from arbitrarily rounding down
intermediate results. The problem now is that I have come
--- Comment #1 from whaley at cs dot utsa dot edu 2007-01-26 16:21 ---
Created an attachment (id=12963)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12963action=view)
Can be compiled to .s as described in report to duplicate error
--
--- Comment #7 from rearnsha at gcc dot gnu dot org 2007-01-26 16:46
---
(In reply to comment #6)
OK. I see now. This seems hard to fix, since it is exposing the current
implementation of a conversion to bool.
No, it's not the 'current implementation', its the way the C and C++
--- Comment #8 from manu at gcc dot gnu dot org 2007-01-26 16:56 ---
(In reply to comment #7)
(In reply to comment #6)
OK. I see now. This seems hard to fix, since it is exposing the current
implementation of a conversion to bool.
No, it's not the 'current implementation',
--- Comment #9 from rearnsha at gcc dot gnu dot org 2007-01-26 17:03
---
(In reply to comment #8)
I meant that the warning is appropriate but
the message is confusing because it is exposing that when doing
bool x = ~b;
we actually do
bool x = (~b != 0);
Or, more
Sometimes, gnu.gcj.convert.BytesToCharsetAdaptor's read method calls
inBuffer.limit(int) with a value that exceeds the buffer capacity. This can be
easily reproduced when BytesToCharsetAdaptor is used with an input byte aray
that does not have to be decoded from the start, but from a greater
--- Comment #1 from kaloian at doganov dot org 2007-01-26 17:15 ---
Created an attachment (id=12964)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12964action=view)
Short test case that demonstrates the problem.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30600
--- Comment #2 from kaloian at doganov dot org 2007-01-26 17:18 ---
(From update of attachment 12964)
The example works fine if you try to create the demo String using the whole
byte array. But if you wish to skip the fist byte this leads to
IllegalArgumentException because of the bad
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2007-01-26 17:25
---
Subject: Bug 30481
Author: jvdelisle
Date: Fri Jan 26 17:25:06 2007
New Revision: 121207
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121207
Log:
2007-01-26 Jerry DeLisle [EMAIL PROTECTED]
PR
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2007-01-26 17:25
---
Subject: Bug 30532
Author: jvdelisle
Date: Fri Jan 26 17:25:06 2007
New Revision: 121207
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121207
Log:
2007-01-26 Jerry DeLisle [EMAIL PROTECTED]
PR
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2007-01-26 17:28
---
Subject: Bug 30481
Author: jvdelisle
Date: Fri Jan 26 17:28:07 2007
New Revision: 121208
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121208
Log:
2007-01-26 Jerry DeLisle [EMAIL PROTECTED]
PR
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2007-01-26 17:28
---
Subject: Bug 30532
Author: jvdelisle
Date: Fri Jan 26 17:28:07 2007
New Revision: 121208
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121208
Log:
2007-01-26 Jerry DeLisle [EMAIL PROTECTED]
PR
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2007-01-26 17:29
---
Fised on 4.2 and 4.3
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2007-01-26 17:30
---
Fixed on 4.2 and 4.3
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-01-26 17:39 ---
First off OpenSSL has undefined code in it so you should report to them, the
following warnings:
evp_pkey.c: In function 'EVP_PKEY2PKCS8_broken':
evp_pkey.c:382: warning: function called through a non-compatible
--- Comment #13 from pinskia at gcc dot gnu dot org 2007-01-26 17:39
---
*** Bug 30596 has been marked as a duplicate of this bug. ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #6 from pinskia at gcc dot gnu dot org 2007-01-26 17:43 ---
(In reply to comment #4)
I have read the documentation, and I understand what the option does. I
compile my complete programme and all its libraries with this option.
You did not compile libc or libm with the
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-01-26 17:49 ---
Use sqrtl then if you don't want the rounding.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #6 from paolo at gcc dot gnu dot org 2007-01-26 18:00 ---
Subject: Bug 30586
Author: paolo
Date: Fri Jan 26 18:00:42 2007
New Revision: 121209
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121209
Log:
2007-01-26 Paolo Carlini [EMAIL PROTECTED]
PR
--- Comment #7 from paolo at gcc dot gnu dot org 2007-01-26 18:03 ---
Subject: Bug 30586
Author: paolo
Date: Fri Jan 26 18:03:44 2007
New Revision: 121210
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121210
Log:
2007-01-26 Paolo Carlini [EMAIL PROTECTED]
PR
--- Comment #3 from sje at gcc dot gnu dot org 2007-01-26 18:16 ---
Subject: Bug 30182
Author: sje
Date: Fri Jan 26 18:16:29 2007
New Revision: 121211
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121211
Log:
PR other/30182
* config/pa/pa.h (TARGET_HPUX_11): New.
This little code
---
const double foo() { return 1.; }
---
used to be fine in C++ even in the presence of -Wreturn-type but now
yields a warning with recent mainline:
deal.II/tests /tmp/bangerth/bin/bin/c++ -Wreturn-type -c x.cc
x.cc:1: warning: type qualifiers ignored on
I get a warning about canonical types like this from one of my codes:
tests/bits /tmp/bangerth/bin/bin/g++ -DHAVE_CONFIG_H -DHAVE_ISNAN -ggdb
-DDEBUG -pedantic -Wall -Wpointer-arith -Wwrite-s
trings -Winline -Woverloaded-virtual -Wsynth -Wsign-compare -Wconversion
-Wswitch -ftemplate-depth-128
--- Comment #7 from kargl at gcc dot gnu dot org 2007-01-26 18:52 ---
(In reply to comment #4)
I have read the documentation, and I understand what the option does. I
compile my complete programme and all its libraries with this option.
You did not compile all of the needed
--- Comment #1 from manu at gcc dot gnu dot org 2007-01-26 18:56 ---
Why am I in the CC list?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30601
I am trying to check memory limit for my application. I am multiplying some
constant with argv[1]. I am getting correct results if my arg[1] is 5000 and
incorrect value if arg[1] is 6000. Infact it is returning samller value when I
multiply with 6000.
my code is as follows:
==
Good day,
Viazzgra $1, 80
Ciazzlis $3, 00
Levizztra $3, 35
http://www.printeryml.*com ( Important ! Remove * )
--
know what it might achieve... but he now concentrated as he had never
done in his life on forcing that bead of light right back into Voldemort
s wand... and slowly... very slowly
--- Comment #3 from tromey at gcc dot gnu dot org 2007-01-26 19:42 ---
I am testing a patch to defer error messages in this situation.
--
tromey at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #37 from rakdver at gcc dot gnu dot org 2007-01-26 19:56
---
Subject: Bug 29516
Author: rakdver
Date: Fri Jan 26 19:56:05 2007
New Revision: 121214
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121214
Log:
PR tree-optimization/29516
*
--- Comment #2 from bangerth at math dot tamu dot edu 2007-01-26 19:58
---
Subject: Re: [4.3 regression] -Wreturn-type warns about more
than what the documentation says
Why am I in the CC list?
I put you there. I assumed that the bug was introduced with your recent
work on
--- Comment #1 from schwab at suse dot de 2007-01-26 20:04 ---
(50L * rowsetSize * recordLength) overflows when long is a 32 bit type.
--
schwab at suse dot de changed:
What|Removed |Added
Compiling the attached class file with -O results is:
$ gcj -findirect-dispatch -O -c CppTreeParser.class
Unable to coalesce ssa_names 7 and 8642 which are marked as MUST COALESCE.
_t_7(ab) and _t_8642(ab)
frysk/expr/CppTreeParser.java: In class 'frysk.expr.CppTreeParser':
--- Comment #1 from mark at gcc dot gnu dot org 2007-01-26 20:35 ---
Created an attachment (id=12965)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12965action=view)
Generated .class byte code file
This is a generated .class file. It has been generated by gcj -C
CppTreeParser.java
--- Comment #3 from manu at gcc dot gnu dot org 2007-01-26 20:50 ---
(In reply to comment #2)
Subject: Re: [4.3 regression] -Wreturn-type warns about more
than what the documentation says
Why am I in the CC list?
I put you there. I assumed that the bug was introduced with
--- Comment #12 from sqrammi at hotmail dot com 2007-01-26 21:10 ---
This was confirmed to be a problem with alignment fixup in the kernel.
Do an 'echo 2 /proc/cpu/alignment' and misaligned accesses are fixed up, and
this problem goes away. Misaligned accesses should IMHO not be
--- Comment #10 from djg at cray dot com 2007-01-26 21:09 ---
(In reply to comment #8)
I'm testing this patch, that makes us more conservative, and concludes that
two
pointers don't overlap only if both are based on restricted pointers, with
based on trivially implemented as the
--- Comment #4 from bangerth at math dot tamu dot edu 2007-01-26 21:11
---
Subject: Re: [4.3 regression] -Wreturn-type warns about more
than what the documentation says
You assumed? Did I do something wrong?
I don't know. Possibly not. But the people who've been working in a
--- Comment #5 from manu at gcc dot gnu dot org 2007-01-26 21:13 ---
(In reply to comment #4)
I'm not accusing you of having caused this. I'm just trying to get anyone
knowledgable about the warning system to help find out who did :-)
OK. That is fine. Just that I am new here and I
--- Comment #6 from gdr at cs dot tamu dot edu 2007-01-26 21:21 ---
Subject: Re: [4.3 regression] -Wreturn-type warns about more than what the
documentation says
bangerth at math dot tamu dot edu [EMAIL PROTECTED] writes:
| Subject: Re: [4.3 regression] -Wreturn-type warns about
--- Comment #6 from ismail at pardus dot org dot tr 2007-01-26 21:29
---
Maybe a better version could be like this,
--- gcc/toplev.c2006-10-09 19:27:14.0 +0300
+++ gcc/toplev.c2007-01-26 20:59:19.395519510 +0200
@@ -1975,6 +1975,12 @@
/* Language-specific
--- Comment #7 from gdr at cs dot tamu dot edu 2007-01-26 21:32 ---
Subject: Re: [4.3 regression] -Wreturn-type warns about more than what the
documentation says
manu at gcc dot gnu dot org [EMAIL PROTECTED] writes:
| OK. That is fine. Just that I am new here and I would like to be
|
--- Comment #8 from bangerth at math dot tamu dot edu 2007-01-26 21:41
---
Subject: Re: [4.3 regression] -Wreturn-type warns about more
than what the documentation says
just assume people are less confrontational than it might appear. :-)
True. Gaby is probably willing to testify
--- Comment #7 from manu at gcc dot gnu dot org 2007-01-26 21:59 ---
Whatever version is fine for me. Gabriel, any preference?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26061
-Wno-tabs according to the manual currently is active for -pedantic, -std=f95,
and -Wall. It should be active for -std=f2003 as well. Finally, it's not
actually active for -pedantic.
% cat xtabs.f90
print *, hi
end
-std=f2003 and -pedantic don't work:
% gfortran -std=f2003 xtabs.f90
%
--- Comment #9 from pinskia at gcc dot gnu dot org 2007-01-26 22:51 ---
I think this was done on purpose.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30601
--- Comment #10 from pinskia at gcc dot gnu dot org 2007-01-26 22:52
---
See PR 18313
*** This bug has been marked as a duplicate of 18313 ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #5 from pinskia at gcc dot gnu dot org 2007-01-26 22:52 ---
*** Bug 30601 has been marked as a duplicate of this bug. ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #11 from bangerth at math dot tamu dot edu 2007-01-26 22:59
---
Subject: Re: [4.3 regression] -Wreturn-type warns about more
than what the documentation says
I think this was done on purpose.
It is contrary to what the documentation says. I think it also doesn't
make
--- Comment #12 from manu at gcc dot gnu dot org 2007-01-26 23:00 ---
Argh! Just when the regression hunt found the patch!
So yes, it was on purpose. And the discussion + review is here:
http://gcc.gnu.org/ml/gcc-patches/2006-11/msg00792.html
--
--- Comment #6 from bangerth at dealii dot org 2007-01-26 23:01 ---
Hm, I'm not sure if I like this situation. Consider this snippet,
typical of template games:
---
template typename T class Array {
T operator();
T operator() const;
};
---
This class
--- Comment #7 from manu at gcc dot gnu dot org 2007-01-26 23:04 ---
Dirk, the patch is missing an update to doc/invoke.texi to reflect the changes.
Would you mind to update it? Thanks.
--
manu at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #5 from manu at gcc dot gnu dot org 2007-01-26 23:14 ---
(In reply to comment #4)
Subject: Re: wrong result
pinskia at gcc dot gnu dot org [EMAIL PROTECTED] writes:
| anther, consider an example definite[2] of 'offsetof', if you think
| that is undefined, it's
--- Comment #8 from hyperquantum at gmail dot com 2007-01-26 23:18 ---
I prefer the second version. The output is only useful in case there are errors
or warnings, not when you have a flawless compilation.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26061
/test/gnu/gcc/objdir/./gcc/xgcc -shared-libgcc -B/test/gnu/gcc/objdir/./gcc
-nos
tdinc++ -L/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/libstdc++-v3/src
-L/test/gn
u/gcc/objdir/hppa2.0w-hp-hpux11.11/libstdc++-v3/src/.libs
-B/opt/gnu/gcc/gcc-4.3
.0/hppa2.0w-hp-hpux11.11/bin/
--- Comment #9 from ismail at pardus dot org dot tr 2007-01-26 23:29
---
There should also be a newline,
--- gcc/toplev.c2006-10-09 19:27:14.0 +0300
+++ gcc/toplev.c2007-01-26 20:59:19.395519510 +0200
@@ -1975,6 +1975,12 @@
/* Language-specific end of
--- Comment #4 from jakub at gcc dot gnu dot org 2007-01-26 23:45 ---
Fixed in SVN.
--
jakub at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #7 from jakub at gcc dot gnu dot org 2007-01-26 23:46 ---
Fixed in SVN.
--
jakub at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #8 from jakub at gcc dot gnu dot org 2007-01-26 23:46 ---
Fixed in SVN.
--
jakub at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from manu at gcc dot gnu dot org 2007-01-26 23:47 ---
(In reply to comment #0)
The error message is basically correct, but there is no `argument' here. The
error message should refer to the return type instead. It might suffice to
simply replace the word `argument'
--- Comment #1 from kargl at gcc dot gnu dot org 2007-01-27 00:01 ---
Created an attachment (id=12966)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12966action=view)
untested patch
Here's an untested patch.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30605
--- Comment #2 from kargl at gcc dot gnu dot org 2007-01-27 00:02 ---
Confirmed. I just attached an untested patch.
--
kargl at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #15 from hjl at lucon dot org 2007-01-27 00:02 ---
Created an attachment (id=12967)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12967action=view)
Part of cp/parser.c without --enable-checking=assert
This is the part of cp/parser.c configured without
--- Comment #16 from hjl at lucon dot org 2007-01-27 00:06 ---
Created an attachment (id=12968)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12968action=view)
Part of cp/parser.c with --enable-checking=assert
This is the part of cp/parser.c configured with
--- Comment #4 from dfranke at gcc dot gnu dot org 2007-01-27 00:08 ---
My doings. I'll look into it.
--
dfranke at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #5 from dfranke at gcc dot gnu dot org 2007-01-27 00:34 ---
As far as I can tell, the BUILD_INFO conditional can not easily be employed as
the info, dvi and pdf targets are generated by automake. The `missing` program
that is run instead should step into the breach. It does,
Thus, two options present themself: ditch automake generated targets, do it
manually as everywhere else or tweak the Makefile.am to touch libgomp.info
before invoking `missing makeinfo`.
Preferences?
This only matters when building from SVN. I say we should just require makeinfo
and
--- Comment #6 from pinskia at physics dot uc dot edu 2007-01-27 00:37
---
Subject: Re: [4.3 regression] build fail in libgomp because makeinfo is
missing
Thus, two options present themself: ditch automake generated targets, do it
manually as everywhere else or tweak the
Given an directory x with two source files:
- x/a.java
public class a extends b { }
- x/b.java
public class b { }
With gcj 4.1.1 it was possible to include x as source patch search dir with -I
and compile as follows:
$ gcj -C -I x x/a.java
With current svn trunk (and ecj1 installed) this
--- Comment #3 from kargl at gcc dot gnu dot org 2007-01-27 00:45 ---
Testing the patch shows -pedantic has found some invalid code
in the testsuite.
--
kargl at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #9 from manu at gcc dot gnu dot org 2007-01-27 01:02 ---
(In reply to comment #8)
Subject: Re: -Wno-deprecated needed also for C
manu at gcc dot gnu dot org wrote:
--- Comment #4 from manu at gcc dot gnu dot org 2007-01-23 00:01
---
The testcase
--- Comment #10 from hpa at zytor dot com 2007-01-27 01:09 ---
Subject: Re: -Wno-deprecated needed also for C
manu at gcc dot gnu dot org wrote:
But it doesn't produce that warning. Is that warning dead code or what?
Apparently so. I think it should have stayed a warning, but
--- Comment #7 from dfranke at gcc dot gnu dot org 2007-01-27 01:11 ---
Third option: include libgomp.info in SVN, then `missing` will just touch it.
Please note: I backported the docs two days ago, 4.2 is now also affected. Did
not know this report existed =(
--
dfranke at gcc dot
--- Comment #11 from manu at gcc dot gnu dot org 2007-01-27 01:38 ---
(In reply to comment #10)
Subject: Re: -Wno-deprecated needed also for C
manu at gcc dot gnu dot org wrote:
But it doesn't produce that warning. Is that warning dead code or what?
Apparently so. I
1 - 100 of 106 matches
Mail list logo
