On Mon, Dec 26, 2005 at 11:34:16PM -0800, Geoff Keating wrote:
> We've had Real Problems with this feature since it was introduced. I
> expect it'll take at least another two or three months before it
> settles down and starts to work on most targets; that's only to be
> expected for such a
I believe the problem is that false (and bool()) have value 0, which is also a
pointer value in C (and in C++). C++ is attempting to do the least surprising
conversion, and in this case getting that 'wrong'. That is why test1 works and
test2 does not. I haven't bothered to check with the standard
>
> On Mon, Dec 26, 2005 at 11:34:16PM -0800, Geoff Keating wrote:
> > We've had Real Problems with this feature since it was introduced. I
> > expect it'll take at least another two or three months before it
> > settles down and starts to work on most targets; that's only to be
> > expecte
On 27/12/2005, at 1:49 AM, Jakub Jelinek wrote:
On Mon, Dec 26, 2005 at 11:34:16PM -0800, Geoff Keating wrote:
We've had Real Problems with this feature since it was introduced. I
expect it'll take at least another two or three months before it
settles down and starts to work on most targets
Snapshot gcc-3.4-20051227 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/3.4-20051227/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 3.4 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
On Tue, Dec 27, 2005 at 02:20:44PM -0800, Geoff Keating wrote:
> I'm not sure what "just fine" definition you're using here. I don't
> think you can say it's been extensively tested, and I'm fairly sure I
> can find a bunch of bugs in it. I have already filed one as gcc.gnu.org/bugzilla/show
On Dec 27, 2005, at 6:36 PM, Jakub Jelinek wrote:
It has nothing to do with libgfortran actually, libgfortran only ever
uses the weak pthread function aliases within libgfortran.
The reason why weakref attribute has been added is primarily libstdc++,
see PR4372, because unlike libgfortran or lib
One significant (philosophical) difference between the floating point
code generated by GCC vs that generated by commercial compilers for
IA-32, is the decision whether or not to hoist floating point constants
on the x87. Or phrased equivalently, whether to allocate an x87 stack
register to hold
Hi,
Could you tell me what it means for 'test for excess errors'?
I run make check-gcc RUNTESTFLAGS='dg.exp' on my machine, and got
many failed tests for these errors on my porting gcc.
Do I need to setup something in order to run these testsuites for my port?
Besides DejaGnu and Tcl.
Thanks.
Eri
>
> Hi,
> Could you tell me what it means for 'test for excess errors'?
> I run make check-gcc RUNTESTFLAGS='dg.exp' on my machine, and got
> many failed tests for these errors on my porting gcc.
That usually means there are some internal compiler errors while
compiling the testcase, look at gcc.
Hello,
I'd like to know since gcc implicitly call memset function to perform
optimization and my c libraries are unusable for now. Can I take
another way? Say don't call memset. How to do that?
Yours,
Eric.
Eric Fisher <[EMAIL PROTECTED]> writes:
> I'd like to know since gcc implicitly call memset function to perform
> optimization and my c libraries are unusable for now. Can I take
> another way? Say don't call memset. How to do that?
In your tm.h file define CLEAR_BY_PIECES_P to always return 1.
(
12 matches
Mail list logo
