[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug report: Compile with Microsoft and Intel compiler

From: Eli Zaretskii
Subject: Re: Bug report: Compile with Microsoft and Intel compiler
Date: Thu, 28 Apr 2005 22:37:33 +0300

> From: =?iso-8859-1?Q?Jerker_B=E4ck?= <address@hidden>
> Cc: <address@hidden>
> Date: Thu, 28 Apr 2005 13:44:20 +0200
> > I need to see the expansion of those macros to be able to help you
> > figure it out.  Can you produce such an expansion (it should be a
> > simple matter of invoking the compiler to produce a preprocessed
> > source)?
> Uh? This is a completely new thing for me. When trying this (switch /P) I
> got .i files (ie file.i). I don't know if this will help:
> extern unsigned long file_timestamp_cons (char const *, time_t, int);
> extern unsigned long file_timestamp_now (int *);
> extern void file_timestamp_sprintf (char *p, unsigned long ts);
> extern unsigned long f_mtime (struct file *file, int search);
> I can send you these files - OK?

Not the entire file, it will be huge.  I need the portion of file.i
that corresponds to the code fragments where the compiler complains
about integer overflow in ORDINARY_MTIME_MAX.

> > Okay, but then please change all the places where exit_code is used to
> > unsigned long.
> ?? What do you mean?

Any variable that gets its value from exit_code should now become
unsigned long, or else the compiler will complain again, right?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]