This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Trying to work around a 16-bit x86 weirdness


On Tue, Oct 21, 2003 at 05:24:08PM +0200, Bernd Jendrissek wrote:
> Should I add a pattern for
> (set (match_operand:HI 0) (match_operand:DI 1)) just so I can catch
> these large CONST_INT's?

No, you should figure out where this thing is created.  It may
need to use trunc_int_for_mode.  On the other hand, ...

> > void g(void)
> > {
> > 	f(42, 17);
> > }
[...]
> > g:
> > 	pushw	%bp
> > 	movw	%sp,%bp
> > 	movw	Don't know how to print
> > (plus:HI (reg/f:HI bp)
> >           (const_int 42000 [0xa410]))

... this looks actively wrong.  Like maybe you've got an
uninitialized data read somewhere.

You'll just have to track it down.  You might try using
valgrind or something...


r~


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]