public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Wei, Wanxia" <v592e@unb.ca>
To: gcc-help@gcc.gnu.org
Subject: Ask for help
Date: Tue, 17 Mar 2009 14:45:00 -0000	[thread overview]
Message-ID: <1237301131.49bfb78bd12ec@webmail.unb.ca> (raw)

Dear Sir/Madam:

I am sorry I met a problem when I used gcc to compile my C program and ran the
executables on servers. I compiled my C program with the following two different ways
with different options.

gcc -m32 -O3 -DNDEBUG -fno-strict-aliasing -static –lm

gcc -m32 –O3 –lm

My problem is that the two executables obtained by using the above two ways have the
same performance on some inputs but have different performance on other inputs. I am
sorry I do not know whether executables with different options should always have the
same performance if the parameters are the same when executing these two executables.
If two executables with different options should always have the same performance, the
different performance of the two executables of my C program means there are bugs in
this program?

Thank you for your time and help. 

Yours sincerely, 

Wanxia Wei

             reply	other threads:[~2009-03-17 14:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 14:45 Wei, Wanxia [this message]
2009-03-17 14:51 ` Andrew Haley
2009-03-17 15:02 ` John Fine
2009-03-17 15:36   ` Wei, Wanxia
2009-03-17 15:42     ` Michael Wieher
2009-03-17 16:05     ` Andrew Haley
2009-03-17 20:13       ` Wei, Wanxia
  -- strict thread matches above, loose matches on Subject: below --
1999-09-26 17:36 Haifeng (Tommy) Shen
1999-09-26 17:50 ` Alexandre Oliva
1999-09-30 23:56   ` Alexandre Oliva
1999-10-01  0:00   ` Alexandre Oliva
1999-09-30 23:56 ` Haifeng (Tommy) Shen
1999-10-01  0:00 ` Haifeng (Tommy) Shen

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=1237301131.49bfb78bd12ec@webmail.unb.ca \
    --to=v592e@unb.ca \
    --cc=gcc-help@gcc.gnu.org \
    --cc=wanxia.wei@unb.ca \
    /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).