public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ferruh.yigit at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/95818] wrong "used uninitialized" warning
Date: Mon, 22 Jun 2020 15:11:59 +0000	[thread overview]
Message-ID: <bug-95818-4-11X2QQkC68@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95818-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95818

--- Comment #2 from Ferruh YIGIT <ferruh.yigit at intel dot com> ---
.i output [1] and .s output [2] below, please let me know if the request was
something else.

[1]
int
iavf_dev_link_update(struct rte_eth_dev *dev,
      __attribute__((__unused__)) int wait_to_complete)
{
 struct rte_eth_link new_link;
 struct iavf_info *vf = (&((struct iavf_adapter *)dev->data->dev_private)->vf);




 switch (vf->link_speed) {
 case 10:
  new_link.link_speed = 10;
  break;
 case 100:
  new_link.link_speed = 100;
  break;
 case 1000:
  new_link.link_speed = 1000;
  break;
 case 10000:
  new_link.link_speed = 10000;
  break;
 case 20000:
  new_link.link_speed = 20000;
  break;
 case 25000:
  new_link.link_speed = 25000;
  break;
 case 40000:
  new_link.link_speed = 40000;
  break;
 case 50000:
  new_link.link_speed = 50000;
  break;
 case 100000:
  new_link.link_speed = 100000;
  break;
 default:
  new_link.link_speed = 0;
  break;
 }

 new_link.link_duplex = 1;
 new_link.link_status = vf->link_up ? 1 :
          0;
 new_link.link_autoneg = !(dev->data->dev_conf.link_speeds &
    (1 << 0));

 if (rte_atomic64_cmpset((uint64_t *)&dev->data->dev_link,
    *(uint64_t *)&dev->data->dev_link,
    *(uint64_t *)&new_link) == 0)
  return -1;

 return 0;
}



[2]
        .globl  iavf_dev_link_update
        .type   iavf_dev_link_update, @function iavf_dev_link_update:
.LFB6034:
        .cfi_startproc
        movq    24(%rdi), %rcx
        movq    96(%rcx), %rsi
        movl    476(%rsi), %edx
        cmpl    $20000, %edx
        je      .L5
        jbe     .L28
        cmpl    $50000, %edx
        je      .L5
        jbe     .L29
        cmpl    $100000, %edx
        movl    $0, %eax
        cmovne  %rax, %rdx
.L5:
        movl    112(%rcx), %eax
        movzbl  473(%rsi), %esi
        notl    %eax
        andl    $1, %eax
        sall    $2, %esi
        leal    1(%rax,%rax), %eax
        orl     %esi, %eax
        andl    $7, %eax
        salq    $32, %rax
        orq     %rax, %rdx
        movq    104(%rcx), %rax
#APP
# 33 "/root/development/dpdk-next-net/build/include/rte_atomic_64.h" 1
        lock ; cmpxchgq %rdx, 104(%rcx);sete %al;
# 0 "" 2
#NO_APP
        cmpb    $1, %al
        sbbl    %eax, %eax
        ret
        .p2align 4,,10
        .p2align 3
.L29:
        cmpl    $25000, %edx
        je      .L5
        cmpl    $40000, %edx
        je      .L5
.L11:
        xorl    %edx, %edx
        jmp     .L5
        .p2align 4,,10
        .p2align 3
.L28:
        cmpl    $1000, %edx
        je      .L5
        jbe     .L30
        cmpl    $10000, %edx
        movl    $0, %eax
        cmovne  %rax, %rdx
        jmp     .L5
        .p2align 4,,10
        .p2align 3
.L30:
        cmpl    $10, %edx
        je      .L5
        cmpl    $100, %edx
        je      .L5
        jmp     .L11
        .cfi_endproc
.LFE6034:
        .size   iavf_dev_link_update, .-iavf_dev_link_update
        .p2align 4

  parent reply	other threads:[~2020-06-22 15:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 12:53 [Bug c/95818] New: " ferruh.yigit at intel dot com
2020-06-22 13:00 ` [Bug c/95818] " rguenth at gcc dot gnu.org
2020-06-22 15:11 ` ferruh.yigit at intel dot com [this message]
2020-06-22 19:29 ` glisse at gcc dot gnu.org
2020-06-22 23:55 ` ferruh.yigit at intel dot com
2020-06-22 23:59 ` ferruh.yigit at intel dot com
2020-06-23  0:21 ` [Bug middle-end/95818] " msebor at gcc dot gnu.org
2020-06-23  0:35 ` ferruh.yigit at intel dot com
2020-06-23  1:58 ` msebor at gcc dot gnu.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=bug-95818-4-11X2QQkC68@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).