public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Humpolicek, Jiri - Acision" <jiri.humpolicek@acision.com>
To: "Tim Prince" <tprince@computer.org>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: gcc warnings
Date: Wed, 17 Oct 2007 14:28:00 -0000	[thread overview]
Message-ID: <53248A54C3B3EC4EAAD993D10A6DD01203C5DDB3@cz-ex002.groupinfra.com> (raw)
In-Reply-To: <47160B5F.9080009@computer.org>

>>             I have, from my point of view, strange problem. I want to
>tell gcc to report all compilation warnings, especially warnings about
>assigment from variable of greater type to variable with smaller type.
For >example, when I write following code and compile it with next
command no >warning is reported:
>> 
>> c++ -o test test.cpp -Wall -Wextra -Wconversion -pedantic
>> 
>You don't say anything about what problem you encounter, or what
>platform you use.  Your source code doesn't look like a suitable
>replacement for a test command which may be implemented in your shell,
>so it would be simpler to choose a non-conflicting name.

I don't understand you. My problem is, that I am not able to force gcc
to report warnings when I assign bigger type to smaller type. So I
decided to ask someone to help me or give me any explanations of this
behaviour.

Jiri Humpolicek


This e-mail and any attachment is for authorised use by the intended recipient(s) only. This email contains confidential information. It should not be copied, disclosed to, retained or used by, any party other than the intended recipient. Any unauthorised distribution, dissemination or copying of this E-mail or its attachments, and/or any use of any information contained in them, is strictly prohibited and may be illegal. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender directly via email. Any emails that you send to us may be monitored by systems or persons other than the named communicant for the purposes of ascertaining whether the communication complies with the law and company policies.

  reply	other threads:[~2007-10-17 14:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17  9:08 Humpolicek, Jiri - Acision
2007-10-17 11:48 ` John Love-Jensen
2007-10-17 11:49 ` Tom St Denis
2007-10-17 14:08   ` Humpolicek, Jiri - Acision
2007-10-17 13:28 ` Tim Prince
2007-10-17 14:28   ` Humpolicek, Jiri - Acision [this message]
2007-10-17 15:25     ` Andrew Haley
  -- strict thread matches above, loose matches on Subject: below --
2008-08-12 15:36 kamelopardus
2008-08-12 15:48 ` Andrew Bell
2008-08-12 15:52   ` Joel Dice
2008-08-12 17:19   ` kamelopardus
2000-05-24 14:29 Zia Babar
2000-05-24 23:48 ` Martin v. Loewis

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=53248A54C3B3EC4EAAD993D10A6DD01203C5DDB3@cz-ex002.groupinfra.com \
    --to=jiri.humpolicek@acision.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=tprince@computer.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).