From: Joel Brobecker <brobecker@adacore.com>
To: Jerome Guitton <guitton@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Alpha/Tru64 maximum debuggable stack frame size
Date: Fri, 23 Apr 2010 14:33:00 -0000 [thread overview]
Message-ID: <20100423143326.GN19194@adacore.com> (raw)
In-Reply-To: <1271951672-23382-1-git-send-email-guitton@adacore.com>
> 2010-04-22 Jerome Guitton <guitton@adacore.com>
>
> * alpha-tdep.c (INSN_OPCODE, MEM_RA, MEM_RB, MEM_DISP, BR_RA)
> (OPR_FUNCTION, OPR_HAS_IMMEDIATE, OPR_RA, OPR_RC, OPR_LIT): New macros.
> (lda_opcode, stq_opcode, bne_opcode, subq_opcode, subq_function):
> New constants.
> (alpha_heuristic_analyze_probing_loop): New function.
> (alpha_heuristic_frame_unwind_cache): In the prologue analysis, detect
> and handle cases when a stack probe loop is generated.
> * alpha-mdebug-tdep.c (alpha_mdebug_frameless): New function.
> (alpha_mdebug_max_frame_size_exceeded): New function.
> (alpha_mdebug_after_prologue): Use alpha_mdebug_frameless.
> (alpha_mdebug_frame_sniffer, alpha_mdebug_frame_base_sniffer):
> Return 0 when the maximum debuggable frame size has been exceeded.
OK, with a few little corrections...
> +/* Return a non-null result if the function is frameless; zero otherwise. */
^^^^
Can you use zero instead of null when you mean integer 0. I noticed
a few places where this needs to be adjusted...
> + return PROC_FRAME_REG (proc_desc) == ALPHA_SP_REGNUM
> + && PROC_FRAME_OFFSET (proc_desc) == 0;
Can you add parentheses around the condition. It's not strictly necessary,
but it's part of the GNU style, because it helps code automatic formatters
such as GNU indent.
return (PROC_FRAME_REG (proc_desc) == ALPHA_SP_REGNUM
&& PROC_FRAME_OFFSET (proc_desc) == 0);
> + return PROC_FRAME_OFFSET (proc_desc) == 0
> + && !alpha_mdebug_frameless (proc_desc);
Same here, please.
> +/* Instruction decoding. The notations for registers, immediates and opcodes
Missing second space after first period.
> + If anything different is found, the function returns without
> + changing PC and FRAME_SIZE. Otherwise, PC will point immediately
Likewise here.
--
Joel
next prev parent reply other threads:[~2010-04-23 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 15:55 Jerome Guitton
2010-04-23 14:33 ` Joel Brobecker [this message]
2010-04-23 15:17 ` Jerome Guitton
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=20100423143326.GN19194@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=guitton@adacore.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).