public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH V2 0/3] Improve insn endianness support in CGEN ports
Date: Fri, 05 Jun 2020 16:10:18 +0200	[thread overview]
Message-ID: <87sgf9zjqt.fsf@oracle.com> (raw)
In-Reply-To: <20200605070339.GW29024@bubble.grove.modra.org> (Alan Modra's message of "Fri, 5 Jun 2020 16:33:39 +0930")


Hi Alan.

    > > These popped up in my overnight testing.  The logs all say
    > > *** stack smashing detected ***: <unknown> terminated
    > > inside build_dis_hash_table.
    > 
    > Never mind, it's unrelated to your patch.
    
    Well, not the additional insn_endian parameters.  But it is no doubt
    this one:
    	* bpf.cpu (define-bpf-isa): Set base-insn-bitsize to 64.

Thanks for the fix.

I was wondering why my regression testing did not catch this, then found
about -fstack-check.  I changed my scripts to use it.

  reply	other threads:[~2020-06-05 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 14:23 Jose E. Marchesi
2020-06-02 14:23 ` [PATCH V2 1/3] opcodes: support insn endianness in cgen_cpu_open Jose E. Marchesi
2020-06-02 14:23 ` [PATCH V2 2/3] opcodes: discriminate endianness and insn-endianness in CGEN ports Jose E. Marchesi
2020-06-02 14:23 ` [PATCH V2 3/3] cpu, gas, opcodes: remove no longer needed workaround from the BPF port Jose E. Marchesi
2020-06-04  9:42 ` [PATCH V2 0/3] Improve insn endianness support in CGEN ports Jose E. Marchesi
2020-06-04 13:29   ` Alan Modra
2020-06-04 14:35     ` Jose E. Marchesi
2020-06-05  3:26     ` Alan Modra
2020-06-05  6:55       ` Alan Modra
2020-06-05  7:03         ` Alan Modra
2020-06-05 14:10           ` Jose E. Marchesi [this message]
2020-06-05 15:51             ` Eric Botcazou

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=87sgf9zjqt.fsf@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    /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).