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]

warning_at -> warning transition: Freeze trunk? Testers needed


Dear all,

I am currently bootstrapping a patch against revision 146956 to make
warning take an explicit location always and hence remove warning_at,
hence finishing this partial transition. Obviously the patch is huge
and everytime a warning is touched, it breaks. Furthermore, I can only
test x86_64-unknown-linux-gnu.

So, I am asking:

Should trunk be frozen until the patch is reviewed + committed to
avoid any breakage? This may be restricted to patches touching
warnings, everything else can still go in.

Can anyone test the patch in different targets?

In any case, fixing any breakage should be trivial (and surely it will
be an obvious patch that doesn't require review).

Cheers,

Manuel.


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