public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joolzg at btinternet dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/49620] piece of code from modification to dvblast but cant get it to compile and run correctly
Date: Sun, 03 Jul 2011 21:51:00 -0000 [thread overview]
Message-ID: <bug-49620-4-V7eA5oWDEn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49620-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49620
--- Comment #4 from julian gardner <joolzg at btinternet dot com> 2011-07-03 21:51:01 UTC ---
(In reply to comment #3)
> A single .o file is not a complete program, it also needs a main() and whatever
> else is needed to call the problematic code and observe whether it worked or
> not.
So you want a buildable executable for a single line of bugged code.
I will try, but what do i do if i cant build a non-working version.
joolz
next prev parent reply other threads:[~2011-07-03 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 19:43 [Bug c/49620] New: " joolzg at btinternet dot com
2011-07-03 20:39 ` [Bug c/49620] " mikpe at it dot uu.se
2011-07-03 21:06 ` joolzg at btinternet dot com
2011-07-03 21:38 ` mikpe at it dot uu.se
2011-07-03 21:51 ` joolzg at btinternet dot com [this message]
2011-07-04 9:42 ` rguenth at gcc dot gnu.org
2011-07-04 10:00 ` redi at gcc dot gnu.org
2011-07-07 7:10 ` joolzg at btinternet dot com
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=bug-49620-4-V7eA5oWDEn@http.gcc.gnu.org/bugzilla/ \
--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).