Re: using -ftracer stops buildworld at shutdown.c

From: Stefan Farfeleder (stefan_at_fafoe.narf.at)
Date: 07/27/05

  • Next message: Rink Springer: "Re: Problem with pic16l_setled" 
    Date: Wed, 27 Jul 2005 15:31:35 +0200
To: jason henson <jason@ec.rr.com>

    On Tue, Jul 26, 2005 at 06:46:55PM -0400, jason henson wrote:

    > To avoid this warning, the variables and/or arguments should be
    > prevented from being optimized by declaring them as volatile.
    >
    > So I sprinkled some volatiles around, but mostly got more errors that
    > said "gcc volatile discards qualifiers from pointer target type" in the
    > fprintf functions.

    Replacing line 276 with 'FILE *volatile pf;' fixes the warning. But the
    usage of {long,set}jmp() is wrong anyway since timeout() can jump back
    into timewarn() while that isn't executed at all.

    Stefan

    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"

  • Next message: Rink Springer: "Re: Problem with pic16l_setled"

    Relevant Pages

    • RE: [PATCH 9/24] make atomic_read() behave consistently on ia64
      ... With this applied together with shuffling the volatile from the ... declaration to the usage and atomic_set ...
      (Linux-Kernel)
    • Re: mutex question
      ... The OP did not mention 'volatile' at all, so I am not even sure what you're ... That is *not* what volatile is for - multithreading is not part of its utility, ... I am condemning its usage though, because it is neither necessary nor sufficient. ... Can your present some VC8 compatible code using volatile for shared access of a variable between threads where _ReadBarrier, _WriteBarrier and Interlocked* wouldn't be more portable to other Windows platforms? ...
      (microsoft.public.win32.programmer.kernel)
    • Re: Interesting GCC optimization, but is it legal if POSIX thread support is claimed?
      ... particular object is not, in fact, volatile. ... Otherwise, not declaring ... object is identified as such to the compiler - the compiler is free to ... execution paths, then that function is free to write to that same ...
      (comp.programming.threads)
    • Re: Why is the kfree() argument const?
      ... volatile No cacheing through this lvalue: each operation in the abstract semantics must ... Since the content of the referenced object is unlikely to be declared volatile, ... Or maybe there is a rationale for never declaring kmalloc to have the ...
      (Linux-Kernel)
    • Re: volatile
      ... It has a similar effect to declaring a member function "const": ... The "this" pointer will point to a "volatile"-qualified equivalent ... Since it knows that foo was not changed from its initial value ... In the above example, foo is now a pointer to volatile int, whose ...
      (comp.lang.cpp)