This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: RFR: Using XNEW.../XCNEW... allocations.
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: Marcin Dalecki <martin at dalecki dot de>
- Cc: gcc-patches List <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 31 Jan 2006 17:53:58 -0500
- Subject: Re: RFR: Using XNEW.../XCNEW... allocations.
- References: <E55A3F76-4A4B-41F1-8EE7-BFB2B0EA61C8@dalecki.de>
On Jan 31, 2006, at 7:20 AM, Marcin Dalecki wrote:
The attached patch is making a lot of places use the libiberty
type-safe
memory allocation wrapper XNEW... macro family. This is making the
code a bit less terse
and more type safe. Everything inside this patch has been
automatically verifyed.
OK to apply to trunk?
This causes a bootstrap failure now that gcc.c does not have
-Wno-error.
The fix is:
[dandelion:local/gcc/gcc] pinskia% svn diff gcc.c
Index: gcc.c
===================================================================
--- gcc.c (revision 110452)
+++ gcc.c (working copy)
@@ -6481,7 +6481,7 @@ main (int argc, char **argv)
/* Record which files were specified explicitly as link input. */
- explicit_link_files = XCNEWVEC (bool, n_infiles);
+ explicit_link_files = XCNEWVEC (char, n_infiles);
if (combine_flag)
combine_inputs = true;
I am bootstrapping this fix right now.
Next time please bootstrap and test your fix.
-- Pinski