On Mon, 2015-12-21 at 19:20 +0100, Marek Polacek wrote:
> On Mon, Dec 21, 2015 at 01:12:33PM -0500, Patrick Palka wrote:
> > GCC 6, compared to GCC 5, now emits an extra newline between error
> > messages. Is this intended?
> >
> > $ cat error.c
> > int x = a;
&
On Mon, Dec 21, 2015 at 01:12:33PM -0500, Patrick Palka wrote:
> GCC 6, compared to GCC 5, now emits an extra newline between error
> messages. Is this intended?
>
> $ cat error.c
> int x = a;
> int y = b;
> $ gcc-5 error.c
> error.c:1:9: error: ‘a’ undeclared here (not
GCC 6, compared to GCC 5, now emits an extra newline between error
messages. Is this intended?
$ cat error.c
int x = a;
int y = b;
$ gcc-5 error.c
error.c:1:9: error: ‘a’ undeclared here (not in a function)
int x = a;
^
error.c:2:9: error: ‘b’ undeclared here (not in a function)
int y
Thanks for your answer. Sorry I used the wrong list.
David
> -Original Message-
> From: fidell...@mykolab.com [mailto:fidell...@mykolab.com]
> Sent: 04 November 2013 14:34
> To: gcc@gcc.gnu.org
> Cc: David Aldrich
> Subject: Re: Why doesn't gcc 4.6 show line nu
On Monday 04 November 2013 13:56:46 David Aldrich wrote:
> EVD.cpp:(.text+0x1c6e): undefined reference to `Matrix
> >::Matrix()'
Because it's the linker which is complaining, not the compiler. "Undefined
reference" means you're referencing a library the linker can't find.
--
Fidel Leon
fidell.
On 11/04/2013 02:56 PM, David Aldrich wrote:
I hope this isn't a silly question. I am running gcc 4.6.3 on Ubuntu 12. When
I compile my source code I get compiler errors in a form that I don't expect.
For example:
EVD.cpp:(.text+0x1c6e): undefined reference to `Matrix
>::Matrix()'
Why is
Hi
I hope this isn't a silly question. I am running gcc 4.6.3 on Ubuntu 12. When
I compile my source code I get compiler errors in a form that I don't expect.
For example:
EVD.cpp:(.text+0x1c6e): undefined reference to `Matrix
>::Matrix()'
Why is the location of the error shown relative to
gold. Can you try updating
>> binutils to
>> the head of the 2.21 branch (or to mainline)? You can probably mitigate
>> the problem by using -flto-partition=none (use a single partition for
>> optimizing
>> at link-time).
>>
>> The .ltransXX files are the w
at link-time (and also reduce the memory footprint
by reducing the size of the TUs GCC has to deal with).
Richard.
Hi Richard,
For what its worth, I got the same error messages using a 04/09/11
snapshot of binutils/gold version 2.21.51 from Debian. So, if its a bug
its still there. I&
On Sun, Apr 10, 2011 at 1:04 AM, Benjamin Redelings I
wrote:
> Hi,
>
> I just tried compiling with LTO for the first time. I can't figure out
> what to try based on the error message below. Is there a HTML page I should
> be looking at?
>
> It seems that this did not work:
>
> g++-4.6 -isyst
Hi,
I just tried compiling with LTO for the first time. I can't figure
out what to try based on the error message below. Is there a HTML page
I should be looking at?
It seems that this did not work:
g++-4.6 -isystem ../../../master/boost/include -ffast-math -DNDEBUG
-DNDEBUG_DP -funr
On 14 May 2010 13:01, Bernd Roesch wrote:
> Hi
>
> I compile the GCC4.5.0 on cygwin and when i use it in cygwin shell, all is ok.
> But when i use it on dev-cpp the output contain some crap chars, because GCC
> output utf8 error
> messages
>
> Is there a way to avoid that
Hi
I compile the GCC4.5.0 on cygwin and when i use it in cygwin shell, all is ok.
But when i use it on dev-cpp the output contain some crap chars, because GCC
output utf8 error
messages
Is there a way to avoid that GCC output text in utf8 ?
Here is dev-cpp source.Its since long time not
On Wed, Aug 26, 2009 at 03:02:44PM -0400, Bradley Lucier wrote:
> On Wed, 2009-08-26 at 20:38 +0200, Paolo Bonzini wrote:
> >
> > > When I worked at AMD, I was starting to suspect that it may be more
> > > beneficial
> > > to re-enable the first schedule insns pass if you were compiling in 64-bit
Bradley Lucier writes:
> and RBX is used by XLAT, XLATB.
XLAT* is generally not used anymore, certainly not in gcc generated code.
> Are 12 registers not enough, in principle, to do scheduling before
> register allocation?
You want to limit gcc to only 12 registers?
> I was getting a 15% sp
On Wed, 2009-08-26 at 17:12 -0700, Ian Lance Taylor wrote:
> If you are getting that kind of speedup (which I personally did not
> expect) then this is clearly worth pursuing. It should be possible to
> make it work at least in 64-bit mode. I recommend that you file a bug
> report or two for cas
Bradley Lucier writes:
> Are 12 registers not enough, in principle, to do scheduling before
> register allocation? I was getting a 15% speedup on some numerical
> codes, as pre-scheduling spaced out the vector loads among the
> floating-point computations.
If you are getting that kind of speedu
On Wed, 2009-08-26 at 20:38 +0200, Paolo Bonzini wrote:
>
> > When I worked at AMD, I was starting to suspect that it may be more
> > beneficial
> > to re-enable the first schedule insns pass if you were compiling in 64-bit
> > mode, since you have more registers available, and the new registers
When I worked at AMD, I was starting to suspect that it may be more beneficial
to re-enable the first schedule insns pass if you were compiling in 64-bit
mode, since you have more registers available, and the new registers do not
have hard wired uses, which in the past always meant a lot of spil
On Wed, Aug 26, 2009 at 06:30:44AM -0700, Ian Lance Taylor wrote:
> Bradley Lucier writes:
>
> > I've never seen the answer to the following question: Why do some
> > versions of gcc that I build not have string substitutions in error
> > messages?
>
> Pe
On Wed, 2009-08-26 at 09:00 -0400, Bradley Lucier wrote:
> I've never seen the answer to the following question: Why do some
> versions of gcc that I build not have string substitutions in error
> messages?
>
> I get things like this:
>
> [luc...@lambda-head li
Bradley Lucier writes:
> I've never seen the answer to the following question: Why do some
> versions of gcc that I build not have string substitutions in error
> messages?
Perhaps you configured with --disable-intl?
> So, is -fschedule-insns an option to be avoided?
-fsche
I've never seen the answer to the following question: Why do some
versions of gcc that I build not have string substitutions in error
messages?
I get things like this:
[luc...@lambda-head lib]$ /pkgs/gcc-mainline/bin/gcc -mcpu=970 -m64 -
fschedule-insns -Wno-unused -O1 -fno-math-
Dave makes a very important point, who to believe:
Certainly System header prototypes, but then the
file, line-number, and prototype which the implementation contradicts,
whenever.
mfg, Brian
* Simon Toth ([EMAIL PROTECTED]) [20080718 13:16]:
> Is there any full database of gcc warnings and errors?
AFAIK, there isn't one. I guess your best choice is gcc.pot (i.e. the
message catalog) in the po subdir.
Philipp
Simon Toth wrote:
I'm currently building a database of gcc warnings and error messages
including a example of code what triggers it and how to fix it.
Is there any full database of gcc warnings and errors?
Simon Toth
For the GNAT front end, no such list exists, however, a grep
of the
I'm currently building a database of gcc warnings and error messages
including a example of code what triggers it and how to fix it.
Is there any full database of gcc warnings and errors?
Simon Toth
SSE/SSE2 enabled
x.i:5: error: Calling 'float(float)' with attribute sseregparm without
SSE/SSE2 enabled
[EMAIL PROTECTED] stack-2]$
Is that possible not to generate duplicated error messages? On stack
alignment branch, I got one more
[EMAIL PROTECTED] stack-2]$
/export/build/gnu/gcc-stack
Hello,
The same programming error gives very different diagnostic using member
function and stand-alone function:
$ cat err1.cc
struct C {
static void f(char const*& p);
};
void b(char* p) {
C::f(const_cast(p));
}
$ cat err2.cc
extern void f(char const*& p);
void b(char* p) {
f(const_cast
'
$
Note that substituting 'int' for 'T' in the only candidate (reported in
error line 2) gives exactly the prototype in error line 1. Yes, the
third error line gives a clue, but the natural way to read error
messages is top-to-bottom, and the first two lines are really
puz
Ralf Schubert wrote:
> is there any reference about the warning- and error-messages gcc (e.g.
> 4.0.1) produces when compiling a C-source code ?
> What I'm looking for is a summary with some explanations. I tried hard,
> but couldn't find something suitable.
We don'
Hi there,
is there any reference about the warning- and error-messages gcc (e.g.
4.0.1) produces when compiling a C-source code ?
What I'm looking for is a summary with some explanations. I tried hard,
but couldn't find something suitable.
Thanks and kind regards
Ralf Schubert
PA
32 matches
Mail list logo
