This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: PATCH: 3.3: sco5 update


> Using single quotes, this:
> 
>     sed      = "/extern \"C\\+\\+\"/N;"
> 
> can be simplified to:
> 
>     sed      = '/extern "C\+\+"/N;'
Ah ok ... and you can concatenate single quoted strings just
the same as double quoted ones? If so it would make the sco_math
fix for __builtin_generic a whole bunch more comprehensible too.
I confess great autogen igorance. Since you wrote it, you
posess great autogen Clue(TM) :)

> This fix:
> +fix = {
> +    hackname = sco_regset;
> +    files    = sys/regset.h;
> +    mach     = "*-*-sco3.2v5*";
> +    select   = "struct[ \t]*fpstate";
> +    sed      = "s/struct[ \t]*fpstate/struct rsfpstate/";
> +    sed      = "s/struct[ \t]*_fpstate/struct _rsfpstate/";
> 
> should be a c-fix:
> 
> +fix = {
> +    hackname = sco_regset;
> +    files    = sys/regset.h;
> +    mach     = "*-*-sco3.2v5*";
> +    select   = "(struct[ \t]+_*)fpstate";
> +    c_fix     = format;
> +    c_fix_arg = "%1rsfpstate";

Ok thanks ... I will update it inmy tree. Since it was part of
a much larger patch set, how would the folks that will (hopefully)
be applying the sco5 patch want me to handle it? Wait for the
larger set to go in and then submit a cleanup patch?

Kean


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]