From 74b35824fc7881eeae6aa22a41c790b5e98f1303 Mon Sep 17 00:00:00 2001 From: Jim Blandy Date: Fri, 26 Oct 2007 23:07:26 +0000 Subject: [PATCH] * ax-gdb.c (gen_cast): Remove redundant assignment to value->type. Doc fix. --- gdb/ChangeLog | 3 +++ gdb/ax-gdb.c | 5 ++--- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 22695494e59..3d5f5f9dcbf 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,8 @@ 2007-10-26 Jim Blandy + * ax-gdb.c (gen_cast): Remove redundant assignment to + value->type. Doc fix. + * ax-general.c (gen_traced_pop, gen_int_literal) (gen_usual_arithmetic): Check for typedefs. diff --git a/gdb/ax-gdb.c b/gdb/ax-gdb.c index 27cc5b1ea35..013b898f1d8 100644 --- a/gdb/ax-gdb.c +++ b/gdb/ax-gdb.c @@ -905,9 +905,8 @@ gen_cast (struct agent_expr *ax, struct axs_value *value, struct type *type) /* We don't have to worry about the size of the value, because all our integral values are fully sign-extended, and when casting pointers we can do anything we like. Is there any - way for us to actually know what GCC actually does with a - cast like this? */ - value->type = type; + way for us to know what GCC actually does with a cast like + this? */ break; case TYPE_CODE_INT: -- 2.30.2