Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: "Cuthbertson, Reva D." <reva_cuthbertson@hp.com>
Cc: <gdb@sources.redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: Question regarding execute_stack_op in dwarf2expr.c
Date: Fri, 21 May 2004 07:50:00 -0000	[thread overview]
Message-ID: <vt2fz9ui5o9.fsf@zenia.home> (raw)
In-Reply-To: <B6C7F31B85669143825614FC8FE64929014C1746@cacexc04.americas.cpqcorp.net>

"Cuthbertson, Reva D." <reva_cuthbertson@hp.com> writes:
> I have a question regarding execute_stack_op() in dwarf2expr.c.  
> In the switch statement where the binary operators are being 
> processed, should there be a "break" after the cases for 
> DW_OP_div and DW_OP_shr?  

Yes!  Thanks for pointing that out.  I've committed the following:

2004-05-21  Jim Blandy  <jimb@redhat.com>

	* dwarf2expr.c (execute_stack_op): Add 'break' statements after
	cases for DW_OP_div and DW_OP_shr.  (Thanks to Reva Cuthbertson.)

Index: gdb/dwarf2expr.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2expr.c,v
retrieving revision 1.11
diff -c -p -r1.11 dwarf2expr.c
*** gdb/dwarf2expr.c	17 Jan 2004 23:09:29 -0000	1.11
--- gdb/dwarf2expr.c	21 May 2004 07:48:13 -0000
*************** execute_stack_op (struct dwarf_expr_cont
*** 575,580 ****
--- 575,581 ----
  		break;
  	      case DW_OP_div:
  		binop = BINOP_DIV;
+                 break;
  	      case DW_OP_minus:
  		binop = BINOP_SUB;
  		break;
*************** execute_stack_op (struct dwarf_expr_cont
*** 595,600 ****
--- 596,602 ----
  		break;
  	      case DW_OP_shr:
  		binop = BINOP_RSH;
+                 break;
  	      case DW_OP_shra:
  		binop = BINOP_RSH;
  		val1 = value_from_longest (signed_address_type (), first);


           reply	other threads:[~2004-05-21  7:50 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <B6C7F31B85669143825614FC8FE64929014C1746@cacexc04.americas.cpqcorp.net>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vt2fz9ui5o9.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=reva_cuthbertson@hp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox