From: Eli Zaretskii <eliz@gnu.org>
To: pipcet@gmail.com
Cc: 46824@debbugs.gnu.org, aaronjensen@gmail.com, akrl@sdf.org
Subject: bug#46824: 28.0.50; nativecomp crash with cl-block/cl-defun
Date: Tue, 02 Mar 2021 17:42:45 +0200 [thread overview]
Message-ID: <83v9a95zpm.fsf@gnu.org> (raw)
In-Reply-To: <83wnup60mn.fsf@gnu.org> (message from Eli Zaretskii on Tue, 02 Mar 2021 17:22:56 +0200)
> Date: Tue, 02 Mar 2021 17:22:56 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 46824@debbugs.gnu.org, aaronjensen@gmail.com, akrl@sdf.org
>
> > > > + gcc_jit_param *params[] =
> > > > + {
> > > > + gcc_jit_context_new_param (comp.ctxt, NULL, comp.void_ptr_type, "buf"),
> > > > + };
> > >
> > > Nitpicking: the braces here should be in column zero.
> >
> > How about we compromise and put them in column two rather than four or zero? :-)
> >
> > (I hope that's what you meant).
>
> Sorry, yes: aligned with first non-whitespace character on the
> previous line.
>
> > I was going to apologize for apparently messing up my cc-mode setup
> > here, but emacs -Q also insists on the incorrect brace placement. We
> > might want to fix that somehow for those Emacs developers who use this
> > "Emacs" thing.
>
> Perhaps submit a bug report against CC Mode.
Btw, my personal workaround for these cases is this:
gcc_jit_param *params[] = {
...;
}
next prev parent reply other threads:[~2021-03-02 15:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 0:34 bug#46824: 28.0.50; nativecomp crash with cl-block/cl-defun Aaron Jensen
2021-02-28 6:13 ` Pip Cet
2021-02-28 6:36 ` Pip Cet
2021-02-28 23:31 ` Aaron Jensen
2021-03-01 9:02 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-01 13:02 ` Pip Cet
2021-03-01 17:04 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-02 9:16 ` Pip Cet
2021-03-02 13:27 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-02 13:27 ` Eli Zaretskii
2021-03-02 14:02 ` Pip Cet
2021-03-02 15:22 ` Eli Zaretskii
2021-03-02 15:42 ` Eli Zaretskii [this message]
2021-03-03 19:39 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-04 7:22 ` Pip Cet
2021-03-04 7:38 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83v9a95zpm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46824@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--cc=akrl@sdf.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).