From: Thomas Koenig <tkoenig@netcologne.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "Tobias Schlüter" <Tobias.Schlueter@physik.uni-muenchen.de>,
gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org,
"Steve Kargl" <sgk@troutmask.apl.washington.edu>,
"Feng Wang" <wf_cs@yahoo.com>,
"Brooks Moses" <brooks.moses@codesourcery.com>
Subject: Re: [PATCH] Fold VIEW_CONVERT_EXPR <type, STRING_CST> generated by Fortran FE a lot (PR target/35366)
Date: Tue, 11 Nov 2008 21:27:00 -0000 [thread overview]
Message-ID: <1226436580.3443.3.camel@meiner.onlinehome.de> (raw)
In-Reply-To: <20081111174931.GG3572@tyan-ft48-01.lab.bos.redhat.com>
On Tue, 2008-11-11 at 18:49 +0100, Jakub Jelinek wrote:
> How is LOGICAL supposed to behave if it is storage associated with an
> integer? Defined only if the integer stored has been 0 or 1, or 0 .false.
> and non-zero .true., or something else?
0 is .false., 1 is .true., anything else is undefined.
We already make use of this in the library. For example, for mask
arguments, we only check the lower byte.
next prev parent reply other threads:[~2008-11-11 20:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 13:27 Jakub Jelinek
2008-11-11 15:40 ` Richard Guenther
2008-11-11 15:53 ` Tobias Schlüter
2008-11-11 16:22 ` Jakub Jelinek
2008-11-11 16:26 ` Tobias Schlüter
2008-11-11 17:21 ` Jakub Jelinek
2008-11-11 17:22 ` Tobias Schlüter
2008-11-11 18:10 ` Jakub Jelinek
2008-11-11 19:07 ` Janne Blomqvist
2008-11-11 19:22 ` Brooks Moses
2008-11-11 19:36 ` Tobias Burnus
2008-11-11 20:50 ` Brooks Moses
2008-11-11 21:38 ` Jakub Jelinek
2008-11-11 21:41 ` Brooks Moses
2008-11-11 21:46 ` Jakub Jelinek
2008-11-11 22:31 ` Brooks Moses
2008-11-11 21:27 ` Thomas Koenig [this message]
2008-11-11 19:17 ` Brooks Moses
2008-11-11 19:34 ` Jakub Jelinek
2008-11-11 19:38 ` Brooks Moses
2008-11-11 17:30 ` Tobias Burnus
2008-11-11 16:22 ` Paul Richard Thomas
2008-11-11 16:45 ` Tobias Schlüter
2008-11-11 21:56 ` Steve Kargl
2008-11-11 22:53 Tobias Burnus
2008-11-12 14:20 ` Jakub Jelinek
2008-11-12 15:34 ` Paul Richard Thomas
2008-11-12 18:09 ` Feng Wang
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=1226436580.3443.3.camel@meiner.onlinehome.de \
--to=tkoenig@netcologne.de \
--cc=Tobias.Schlueter@physik.uni-muenchen.de \
--cc=brooks.moses@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=sgk@troutmask.apl.washington.edu \
--cc=wf_cs@yahoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).