I have not, but that looks like it would be helpful. That would be great if the source translator could just emit code to keep those warnings quiet automatically. I'll add your comment to the ticket so we don't lose track. thanks, -Phil On 02/12/2014 04:46 PM, Gauntt, Nathan E wrote:

Have you tried gcc's #pragma diagnostic push/pop?

http://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Pragmas.html

-Nate

Nate Gauntt HP Contractor Sandia / CSRI (505) 844-0707, (505) 250-5659 cell. [email protected]

On Feb 12, 2014, at 2:32 PM, aesop <[email protected]> wrote:

...

#66: unusual warnings produced by aecc with gcc 4.8 or higher ---------------------------+------------------------------------------------ Reporter: carns | Owner: Type: defect | Status: new Priority: minor | Component: parser Version: git repository | Keywords: ---------------------------+------------------------------------------------

Comment(by carns):

A workaround to this problem is to add "-fno-diagnostics-show-caret" to the CFLAGS of aesop and/or the project that you are compiling with aesop.

This option is only valid for gcc 4.8+, so we can't make it a default part of the aecc scripts.

I'm leaving this ticket open for now because there is really a more fundamental issue of how prevent aecc from showing warnings that are introduced as an artifact of source translation. Right now it just uses grep to filter certain warnings (which is why these partial messages show up with gcc 4.8).

-- Ticket URL: <https://trac.mcs.anl.gov/projects/aesop/ticket/66#comment:1> aesop <https://trac.mcs.anl.gov/projects/aesop> The Aesop Language _______________________________________________ ASG mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/asg

---

ASG mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/asg