This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: print_npx_status_word
- From: Tom Tromey <tromey at redhat dot com>
- To: "Baars\, M.J." <mjbaars1977 dot gdb at gmail dot com>
- Cc: gdb at sourceware dot org, gdb-patches at sourceware dot org, Mark Kettenis <mark dot kettenis at xs4all dot nl>
- Date: Mon, 18 Apr 2011 11:03:47 -0600
- Subject: Re: print_npx_status_word
- References: <4DA7166F.10302@gmail.com> <m3aafshl6l.fsf@fleche.redhat.com> <4DA7ED79.3000400@gmail.com> <m3ei53efd8.fsf@fleche.redhat.com> <4DA87235.7060003@gmail.com> <m3pqoncw78.fsf@fleche.redhat.com> <4DA87479.50203@gmail.com> <m3lizbcvt7.fsf@fleche.redhat.com> <4DA93270.6030708@gmail.com> <201104160824.p3G8ONWV006175@glazunov.sibelius.xs4all.nl> <4DA99DA1.2090708__5871.13250880993$1302961604$gmane$org@gmail.com>
>>>>> "Michael" == Baars, M J <mjbaars1977.gdb@gmail.com> writes:
Michael> Oops... did I remove one of your entries in the ChangeLog? :)
As others have noted, ChangeLog is "prepend only".
We generally don't edit old entries.
Michael> +struct
Michael> +{
Michael> + char *tag;
Michael> + char *description;
Michael> +}
Wrong indentation here, should be 2 spaces.
Fields should have descriptive comments.
I think the struct should have a tag and be terminated here.
Also the fields should be "const".
Michael> +static const npx_exception_flags[6] =
Michael> +
Michael> +{
Michael> + {"IE", "invalid operation"},
Wrong indentation. This is a problem in the whole patch.
Michael> +// print the numeric coprocessor extension (npx) status word
No `//' comments.
Comments should be full sentences, see GNU standards.
Michael> +void print_npx_status_word(uint16_t npx_status_word, struct ui_file *file)
Newline after "void".
Space before "(" -- a problem in a few spots.
Again, GNU standards.
Tom