From: Bruno Haible <bruno@clisp.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 36370@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>,
bug-gnulib@gnu.org
Subject: bug#36370: 27.0.50; XFIXNAT called on negative numbers
Date: Sat, 29 Jun 2019 12:31:27 +0200 [thread overview]
Message-ID: <2515002.Q0mBYvUW8C__23902.1847768285$1561804335$gmane$org@omega> (raw)
In-Reply-To: <CAOqdjBcNA4mDiwsd_jbeePGMdUwPvkFCNdgtZvmiQnYmJNR3pA@mail.gmail.com>
Pip Cet wrote:
> I would like to state that the current assume does
> behave very badly when combined with -fno-inline-small-functions
> -fno-inline.
Since we can't address this limitation through an acceptable change
to the 'assume' macro, we need to address it through documentation.
> marking it
> as __attribute__((always_inline)) is problematic because it might
> directly contradict what the programmer was trying to achieve by
> passing -fno-inline.
__attribute__((always_inline)) exists precisely to make a distinction
between functions where inlining is usually desirable vs. functions
where inlining is essential. We don't need to warn against the uses
of __attribute__((always_inline)) -- confusing behaviour in the debugger
etc. -- becauses these drawbacks are already well-known.
Paul Eggert wrote:
> I suggest something simpler and a little more general. The Emacs documentation
> for 'eassume' says this:
>
> This can improve performance in some cases,
> though it can degrade performance in others. It's often suboptimal
> for COND to call external functions or access volatile storage.
>
> and we could migrate that into the documentation for 'assume'.
As a user of the 'assume' macro, I want a definitive statement about what
I need to provide so that the macro works in the sense of improved performance.
A statement about "often" is too vague.
How about this proposed patch?
diff --git a/lib/verify.h b/lib/verify.h
index f8e4eff..ed1ba19 100644
--- a/lib/verify.h
+++ b/lib/verify.h
@@ -261,7 +261,10 @@ template <int w>
/* Assume that R always holds. This lets the compiler optimize
accordingly. R should not have side-effects; it may or may not be
- evaluated. Behavior is undefined if R is false. */
+ evaluated. The behavior is undefined if R is false.
+ If you want the use of this macro to improve, not deteriorate,
+ performance, R should not contain function calls except to functions
+ that are declared 'inline __attribute__((__always_inline__))'. */
#if (__has_builtin (__builtin_unreachable) \
|| 4 < __GNUC__ + (5 <= __GNUC_MINOR__))
next prev parent reply other threads:[~2019-06-29 10:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 5:36 bug#36370: 27.0.50; XFIXNAT called on negative numbers Pip Cet
2019-06-27 1:10 ` Paul Eggert
2019-06-27 6:16 ` Pip Cet
2019-06-27 8:28 ` Paul Eggert
2019-06-27 13:17 ` Pip Cet
2019-06-27 13:37 ` Eli Zaretskii
2019-06-27 19:38 ` Paul Eggert
2019-06-27 19:56 ` Pip Cet
2019-06-27 21:13 ` Paul Eggert
[not found] ` <5284eb58-3560-da42-d1d1-3bdb930eae49@cs.ucla.edu>
2019-06-27 21:37 ` Pip Cet
2019-06-27 23:45 ` Bruno Haible
[not found] ` <2715311.ceefYqj39C@omega>
2019-06-28 0:04 ` Paul Eggert
2019-06-28 11:06 ` Pip Cet
2019-06-28 12:14 ` Bruno Haible
[not found] ` <8979488.cRkkfcT1mV@omega>
2019-06-28 12:29 ` Bruno Haible
2019-06-28 13:51 ` Pip Cet
[not found] ` <CAOqdjBfS99UpLZ-qLe4=FMXMsr+T3LUvJEsf_gfmF6wwLbqgOw@mail.gmail.com>
2019-06-28 17:46 ` Paul Eggert
2019-06-28 19:11 ` Bruno Haible
[not found] ` <a293f2fe-99b3-3776-f27b-35e3a93d1d34@cs.ucla.edu>
2019-06-28 19:15 ` Pip Cet
2019-06-28 19:56 ` Bruno Haible
2019-06-28 21:08 ` Pip Cet
2019-06-29 5:41 ` Paul Eggert
[not found] ` <87168b28-192b-6666-e9b6-9cdc2ed3917a@cs.ucla.edu>
2019-06-29 6:48 ` Pip Cet
[not found] ` <CAOqdjBfcNbXFw3Fb0wgRR10PNbkJQ+88ObE9KEghLSb-ptdrbA@mail.gmail.com>
2019-06-29 17:31 ` Paul Eggert
[not found] ` <791ae316-3a6f-605a-0da5-874fe3d224c5@cs.ucla.edu>
2019-06-30 9:21 ` Pip Cet
[not found] ` <11002295.LrvMqknVDZ@omega>
2019-06-28 21:07 ` Pip Cet
2019-06-28 23:30 ` Bruno Haible
[not found] ` <2067160.1HRgjLhtDS@omega>
2019-06-29 5:40 ` Paul Eggert
2019-06-29 5:44 ` Pip Cet
[not found] ` <CAOqdjBcNA4mDiwsd_jbeePGMdUwPvkFCNdgtZvmiQnYmJNR3pA@mail.gmail.com>
2019-06-29 10:31 ` Bruno Haible [this message]
[not found] ` <2515002.Q0mBYvUW8C@omega>
2019-06-29 17:11 ` Paul Eggert
[not found] ` <99bacb9f-1192-1315-85d7-5ab4924dfef8@cs.ucla.edu>
2019-06-29 17:48 ` Bruno Haible
2019-06-30 15:30 ` Pip Cet
[not found] ` <CAOqdjBeiMno7nGKwk7SSZQob+CTyG39KRTM9EEebq7NQavLR-Q@mail.gmail.com>
2019-06-30 15:45 ` Bruno Haible
2019-07-02 23:39 ` Paul Eggert
2019-07-01 1:46 ` Richard Stallman
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='2515002.Q0mBYvUW8C__23902.1847768285$1561804335$gmane$org@omega' \
--to=bruno@clisp.org \
--cc=36370@debbugs.gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=pipcet@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.