Project

General

Profile

Actions
Copy link

Bug #5556

closed

CIF misses static keyword for local declarations

Added by Vadim Mutilin over 9 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
High
Assignee:
Evgeny Novikov
Category:
C back-end
Start date:
01/14/2015
Due date:
% Done:

0%

Estimated time:
Detected in build:
ldv-v0.7
Platform:
Published in build:

Description

If the original code contain local static declaration, like (add_chan function)

134 static int add_chan(struct pppox_sock *sock)
135 {
136         static int call_id;

CIF prints output code without static, for example
static int add_chan(struct pppox_sock *sock)
{
  int call_id;

Actions
Copy link
 #1

Updated by Evgeny Novikov over 9 years ago

  • Status changed from New to Open
  • Assignee set to Evgeny Novikov
  • Priority changed from Low to Normal

That is actually an important bug since CIF (C-backend) changes program behavior - static local variables preserve their values after functions exit and those values are used later when corresponding functions are called.

Actions
Copy link
 #2

Updated by Evgeny Novikov about 8 years ago

  • Category set to C back-end
  • Priority changed from Normal to High
Actions
Copy link
 #3

Updated by Evgeny Novikov almost 2 years ago

  • Status changed from Open to Closed

I fixed this very old bug at last in dce15c3. It helps to get rid of 2 false alarms detected for Linux 5.19-rc7.

Actions
Copy link

Also available in: Atom PDF