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: Problem with std_expand_builtin_va_start on targets where sizetype and ptr_type_node don't have the same mode

From: "Zack Weinberg" <zackw at panix dot com>
To: "Andrew Pinski" <pinskia at gmail dot com>
Cc: "GCC Development" <gcc at gcc dot gnu dot org>, "DJ Delorie" <dj at redhat dot com>
Date: Thu, 5 Jul 2007 15:36:14 -0700
Subject: Re: Problem with std_expand_builtin_va_start on targets where sizetype and ptr_type_node don't have the same mode
References: <eb97335b0707051439m1a916d0eid9dd1b675cc683ac@mail.gmail.com> <de8d50360707051528p756ee8c0i85878215ed1a3c8d@mail.gmail.com>

I'll try your patch, but I would still like to know whether we
couldn't stop using make_tree altogether, just expand valist and then
pass it to emit_move_insn (or maybe convert_move would be better).

zw

Follow-Ups:
- Re: Problem with std_expand_builtin_va_start on targets where sizetype and ptr_type_node don't have the same mode
  - From: Zack Weinberg

References:
- Problem with std_expand_builtin_va_start on targets where sizetype and ptr_type_node don't have the same mode
  - From: Zack Weinberg
- Re: Problem with std_expand_builtin_va_start on targets where sizetype and ptr_type_node don't have the same mode
  - From: Andrew Pinski

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