This is the mail archive of the
mailing list for the GCC project.
Re: [patch]: builtin_memset support (replace clrmem by setmem)
- From: Falk Hueffner <falk at debian dot org>
- To: Adrian Straetling <straetling at de dot ibm dot com>
- Cc: Richard Henderson <rth at redhat dot com>, gcc-patches at gcc dot gnu dot org, uweigand at de dot ibm dot com, denisc at overta dot ru, aldyh at redhat dot com, law at redhat dot com, geoffk at geoffk dot org
- Date: Tue, 28 Jun 2005 21:43:01 +0200
- Subject: Re: [patch]: builtin_memset support (replace clrmem by setmem)
- References: <20050628185911.GA18178@de.ibm.com>
Adrian Straetling <email@example.com> writes:
> This updated patch replaces the 'clrmem' pattern by a new 'setmem'
> pattern which handles arbitrary byte values to initialize the storage.
> In a follow-up patch S/390 will make use of that.
> Index: gcc/config/alpha/alpha.md
> + /* If value to set is not zero, use the library routine. */
> + if (operands != const0_rtx)
> + FAIL;
The comment is somewhat confusing, since OTS$ZERO is a library
Also, Tru64 has _OtsFill; I suppose OpenVMS has OTS$FILL then, which
could be used here. If calling conventions are the same, then the byte
needs to be zero-extended in register 18. I have no idea whether it's
worth bothering, though.