Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joern Rennecke <amylaar@cambridge.redhat.com>
To: aoliva@redhat.com (Alexandre Oliva)
Cc: amylaar@redhat.com (Joern Rennecke),
	wilson@cygnus.com (Jim Wilson),
	gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: C++ ptrmemfun break if FUNCTION_BOUNDARY < 2 * BITS_PER_UNIT
Date: Mon, 09 Apr 2001 13:42:00 -0000	[thread overview]
Message-ID: <200104092042.f39KghW01068@phal.cambridge.redhat.com> (raw)
In-Reply-To: <orn19pu921.fsf@guarana.lsd.ic.unicamp.br>

> Doh.  Never mind.  I *does* work.  It's TRUNC_DIV that doesn't, for
> what I need.  I really need a right shift with sign extension:

I was talking about signed division.  I.e. TRUNC_DIV.  So we agree on
that point.

> Does RSHIFT_EXPR guarantee the preservation of the most significant
> (sign) bit?  Does it guarantee the semantics above?

According to c-tree.texi, it does.


  reply	other threads:[~2001-04-09 13:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200104062005.NAA13684@wilson.cygnus.com>
2001-04-09  8:19 ` Alexandre Oliva
2001-04-09 12:29   ` Joern Rennecke
2001-04-09 13:12     ` Alexandre Oliva
2001-04-09 13:42       ` Joern Rennecke [this message]
2001-04-18  5:48       ` Richard Earnshaw
2001-04-18 12:11         ` Alexandre Oliva
2001-04-10  9:27   ` C++ ptrmemfun break if FUNCTION_BOUNDARY < 2 *BITS_PER_UNIT Mark Mitchell
2001-04-17 10:38   ` C++ ptrmemfun break if FUNCTION_BOUNDARY < 2 * BITS_PER_UNIT Andrew Cagney
2001-04-17 13:02     ` Daniel Berlin
2001-05-16  4:53       ` Jason Merrill
2001-05-16  7:18         ` Daniel Berlin

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=200104092042.f39KghW01068@phal.cambridge.redhat.com \
    --to=amylaar@cambridge.redhat.com \
    --cc=amylaar@redhat.com \
    --cc=aoliva@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=wilson@cygnus.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