From: Charles Forsyth <charles.forsyth@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] non-interruptible temporary: why do we care?
Date: Thu, 17 Jun 2021 20:32:15 +0100 [thread overview]
Message-ID: <CAOw7k5i8TekRNtkVsGSp4WWY1oCGEvfn22ntwckXG76Jp1qvWw@mail.gmail.com> (raw)
In-Reply-To: <2484945A14B69F5196BABCD506615017@eigenstate.org>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
yes, I'm not sure why it doesn't do that, but probably if I try to add that
code I'll soon find out!
On Wed, Jun 16, 2021 at 9:29 PM <ori@eigenstate.org> wrote:
> Quoth unobe@cpan.org:
> > Quoth ori@eigenstate.org:
> > > Our compilers will sometimes produce a warning about
> > > a non-interruptible temporary:
> > > ...
> > > Why do we warn about non-interruptible
> > > temporaries? What issues am I missing?
> >
> > Silence to this question means no one knows, right?
> >
>
> I pinged Charles off list and got a response -- it means
> we're falling into the rathole; in other words, we're
> accessing a global variable.
>
> The right thing to do (IMO) is make the compiler allocate
> on the stack, and then the warning would be unneded.
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tdcfb8f84c90eb199-M8efb875683ddcb305946ecdd
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2430 bytes --]
next prev parent reply other threads:[~2021-06-17 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 3:32 ori
2021-06-16 20:23 ` unobe
2021-06-16 20:28 ` ori
2021-06-17 19:32 ` Charles Forsyth [this message]
2021-06-16 21:10 ` Anthony Martin
2021-06-16 21:28 ` unobe
2021-06-20 14:53 ` [9fans] help Spock via 9fans
2021-06-20 15:32 ` Marshall Conover
2021-06-20 18:46 ` U Cirello
2021-06-20 21:14 ` Ethan Gardener
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=CAOw7k5i8TekRNtkVsGSp4WWY1oCGEvfn22ntwckXG76Jp1qvWw@mail.gmail.com \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).