From: Bernd Schmidt <bschmidt@redhat.com>
To: Steve Ellcey <sellcey@imgtec.com>, gcc-patches@gcc.gnu.org
Cc: matthew.fortune@imgtec.com, clm@codesourcery.com
Subject: Re: [Patch, MIPS] Frame header optimization for MIPS (part 2)
Date: Tue, 20 Oct 2015 23:37:00 -0000 [thread overview]
Message-ID: <5626C664.7030006@redhat.com> (raw)
In-Reply-To: <befba71c-8b02-4ee9-b93b-2d7087b955b0@BAMAIL02.ba.imgtec.org>
On 10/16/2015 10:21 PM, Steve Ellcey wrote:
> Here is the second part of the MIPS frame header optimization patch.
I'll leave reviewing the functionality to the MIPS maintainers. But...
> + return TARGET_OLDABI && flag_frame_header_optimization && (optimize > 0);
> + if ((fn != NULL) && fn->machine->optimize_call_stack)
> + if (TARGET_OLDABI
> + && (optimize > 0)
> + && flag_frame_header_optimization
> + && !MAIN_NAME_P (DECL_NAME (current_function_decl))
> + && (cfun->machine->varargs_size == 0)
> + && (crtl->args.pretend_args_size == 0)
> + && (frame->var_size == 0)
> + && (frame->num_acc == 0)
> + && (frame->num_cop0_regs == 0)
> + && (frame->num_fp == 0)
> + && (frame->num_gp > 0)
> + && (frame->num_gp <= MAX_ARGS_IN_REGISTERS)
> + && (!GENERATE_MIPS16E_SAVE_RESTORE)
> + && (!cfun->machine->interrupt_handler_p)
> + && (cfun->machine->does_not_use_frame_header)
> + && (cfun->machine->optimize_call_stack)
> + && (!cfun->machine->callers_may_not_allocate_frame)
> + && !mips_cfun_has_cprestore_slot_p ())
> + return ((cfun->machine->frame.total_size == 0)
> + && !cfun->machine->use_frame_header_for_callee_saved_regs);
There are many unnecessary parentheses in this patch which should be
removed.
Bernd
next prev parent reply other threads:[~2015-10-20 22:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 21:08 Steve Ellcey
2015-10-20 23:37 ` Bernd Schmidt [this message]
2015-10-21 17:43 ` Mike Stump
2015-10-21 18:46 ` Bernd Schmidt
2015-10-21 19:42 ` Steve Ellcey
2015-10-21 21:31 ` Joseph Myers
2015-10-21 21:37 ` Bernd Schmidt
2015-10-21 21:57 ` Joseph Myers
2015-10-23 18:12 ` Steve Ellcey
2015-11-24 18:50 ` Moore, Catherine
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=5626C664.7030006@redhat.com \
--to=bschmidt@redhat.com \
--cc=clm@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=matthew.fortune@imgtec.com \
--cc=sellcey@imgtec.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).