1 Feb 10:55
[RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
Pekka Enberg <penberg <at> kernel.org>
2012-02-01 09:55:51 GMT
2012-02-01 09:55:51 GMT
From: Linus Torvalds <torvalds <at> linux-foundation.org> On Tue, Aug 30, 2011 at 10:43 AM, Jeff Garzik <jeff <at> garzik.org> wrote: > * if someone knows how to access a function declaration, I can solve the > varargs problem Hmm. Right now we do not have access to the function declaration at linearize time. We've checked that the arguments match, and we've cast the arguments to the right types (evaluate.c), so the thinking was that you just use the arguments as-is. But if llvm needs the declaration of a function, we'd need to squirrel it away. Cc: Benjamin Herrenschmidt <benh <at> kernel.crashing.org> Cc: Christopher Li <sparse <at> chrisli.org> Cc: Jeff Garzik <jgarzik <at> redhat.com> Cc: Linus Torvalds <torvalds <at> linux-foundation.org> [ penberg <at> kernel.org: Fix validation/context.c breakage. ] Signed-off-by: Pekka Enberg <penberg <at> kernel.org> --- linearize.c | 8 ++++++++ linearize.h | 1 + 2 files changed, 9 insertions(+), 0 deletions(-) diff --git a/linearize.c b/linearize.c index 1899978..7d57474 100644 --- a/linearize.c +++ b/linearize.c @@ -1195,6 +1195,7 @@ static pseudo_t linearize_call_expression(struct entrypoint *ep, struct expressi struct instruction *insn = alloc_typed_instruction(OP_CALL, expr->ctype);(Continue reading)
RSS Feed