Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This works (gcc version 4.6.1):</p> <pre><code>#ifdef __GNUC__ #define SUPPRESS_NOT_USED_WARN __attribute__ ((unused)) #else #define SUPPRESS_NOT_USED_WARN #endif void foo() { } SUPPRESS_NOT_USED_WARN static void bar() { } int main() { return 0; } /* or static void SUPPRESS_NOT_USED_WARN bar() { } etc. */ /* but not, undefined declarations: SUPPRESS_NOT_USED_WARN static void bar(); */ </code></pre> <p>(Edit:)<br /> <a href="http://gcc.gnu.org/onlinedocs/gcc-4.2.4/gcc/Variable-Attributes.html#Variable-Attributes">GCC v4.2.4 doc. 5.32 Specifying Attributes of Variables</a>:</p> <blockquote> <p>unused<br /> &nbsp; &nbsp; &nbsp; &nbsp; This attribute, attached to a variable, means that the variable is meant to be possibly unused. GCC will not produce a warning for this variable. </p> </blockquote> <p>(Edit.2:)<br /> <a href="http://gcc.gnu.org/onlinedocs/gcc-4.2.4/gcc/Function-Attributes.html#Function-Attributes">GCC v4.2.4 doc. 5.25 Declaring Attributes of Functions</a> (a more correct link, functions, sorry about that.)</p> <blockquote> <p>unused<br /> &nbsp; &nbsp; &nbsp; &nbsp; This attribute, attached to a function, means that the function is meant to be possibly unused. GCC will not produce a warning for this function. </p> </blockquote> <hr> <p>When it comes to <code>pragma push</code> and <code>pop</code> etc the documentation say: </p> <p><a href="http://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Pragmas.html">GCC doc. 6.57.10 Diagnostic Pragmas</a>:</p> <blockquote> <p>Modifies the disposition of a diagnostic. Note that not all diagnostics are modifiable; at the moment only warnings (normally controlled by `-W...') can be controlled, and not all of them. Use -fdiagnostics-show-option to determine which diagnostics are controllable and which option controls them.</p> </blockquote> <p>It states; <em>"and not all of them"</em>, <code>-Wunused-function</code> seems to be one of the ones not willing to be suppressed. The option <code>fdiagnostics-show-option</code> seems to be enabled by default. (Gives the flag from which the error/warning enabled.).</p> <p>Using <code>-Wno-unused-function</code> at command line disables it, but then of course for all, not just the ones directly specified in the code.</p> <p>If you say:</p> <blockquote> <p>gcc -Wunused-function -o o mycode.c</p> </blockquote> <p>You'll still get the warning, - so it does not have anything to do with ie <code>-Wall</code> setting the compile process in an special state where it won't work.</p> <hr> <p>As an example this works:</p> <pre><code>int foo(int i) { return i; } int main() { int a; #pragma GCC diagnostic push #pragma GCC diagnostic ignored "-Wuninitialized" foo(a); #pragma GCC diagnostic pop return 0; } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POStrange diagnostic pragma behavior in GCC 4.6
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMorpfh
    1. USMorpfh
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POStrange diagnostic pragma behavior in GCC 4.6
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks. Using the `unused` attribute is more elegant, and less visually distracting, too. I think that when the documentation says not all warnings can be controlled, it means that not all warnings have `-W...` syntax, not that some warnings that do have `-W...` syntax still cannot be turned off. So I suspect the explanation Adam Rosenfield provided (in his comment) explains why my approach was not going to work. As you say, other `GCC diagnostic ignored ...` pragmas work with `push` and `pop`--I am able to disable `-Wuninitialized` as in your example. Thanks again!
      singulars
      1. PO
      1. USEliah Kagan
    2. COYes, Mr. Rosenfield's explanation sounds good. Had a quick peek at the gcc source code and it seems, tho I've easily can have overlooked something ;), that this is the case. Guess, perhaps, using a #ifdef SILENCE_WARN_FN_UNUSED, or similar could be wise, - to force one to add / make aware / remember etc. at compile-time.
      singulars
      1. PO
      1. USMorpfh
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload