public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "snes2002 at freenet dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/36081] gcc optimizations and threads (pthread)
Date: Tue, 29 Apr 2008 19:06:00 -0000	[thread overview]
Message-ID: <20080429190608.7127.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36081-16127@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from snes2002 at freenet dot de  2008-04-29 19:06 -------
Subject: Re:  gcc optimizations and threads (pthread)

thanks for the quick reply.

But this code works without opimizations. Even with complex constructs.
For the solution of my problem i can't use lock's.
I don't want so serialize the threads, I want to use all 2 processors of my
dual-core.
And for syncing the threads, that's the easiest way.

Works fine whithout optimizations and also works with borland c++-compiler with
all optimizations.


----- original Nachricht --------

Betreff: [Bug driver/36081] gcc optimizations and threads (pthread)
Gesendet: Di 29 Apr 2008 20:55:20 CEST
Von: "pinskia at gcc dot gnu dot org"<gcc-bugzilla@gcc.gnu.org>

> 
> 
> ------- Comment #2 from pinskia at gcc dot gnu dot org  2008-04-29 18:54
> -------
> This is correct behavior, you need either use volatile or use locks.
> 
> 
> -- 
> 
> pinskia at gcc dot gnu dot org changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> 
>              Status|UNCONFIRMED                 |RESOLVED
>          Resolution|                            |INVALID
> 
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36081
> 
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
> 

--- original Nachricht Ende ----


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36081


  parent reply	other threads:[~2008-04-29 19:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 18:52 [Bug driver/36081] New: " snes2002 at freenet dot de
2008-04-29 18:55 ` [Bug driver/36081] " snes2002 at freenet dot de
2008-04-29 18:55 ` pinskia at gcc dot gnu dot org
2008-04-29 18:56 ` snes2002 at freenet dot de
2008-04-29 18:57 ` snes2002 at freenet dot de
2008-04-29 18:58 ` snes2002 at freenet dot de
2008-04-29 19:00 ` snes2002 at freenet dot de
2008-04-29 19:06 ` snes2002 at freenet dot de [this message]
2008-04-29 19:12 ` pinskia at gcc dot gnu dot org
2008-04-30 12:26 ` snes2002 at freenet dot de
2008-05-03 10:27 ` snes2002 at freenet dot de
2008-05-03 11:04 ` rguenth at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080429190608.7127.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).