This is the mail archive of the gcc@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] |
Ian Lance Taylor <iant@google.com> writes:Let's do that.
We've already talked about keeping track of the source location of each #pragma, and searching them for the "state" at a given line. The diagnostic machinery seems to be able to tell what file/line each diagnostic is for, we should be able to scan the pragma list to see what right thing to do is. I think this would be far easier than trying to queue up all the diagnostics and *then* scan the list.
How do you know that code motion will not move things across the pragmas in a backwards direction?
Assuming we've fully converted to the single-integer source location.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |