according to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56301#c3 this
is not an issue with GCC, but job_new shouldn't be marked with the
malloc attribute. The following patch lets the test case pass without
the GCC change reverted. Maybe other usages of the malloc attribute
should be revisited.
--- init/job.h.orig 2012-12-04 17:14:47.000000000 +0000
+++ init/job.h 2013-02-18 13:06:31.792691230 +0000
@@ -165,7 +165,7 @@
NIH_BEGIN_EXTERN
Job * job_new (JobClass *class, const char *name)
- __attribute__ ((warn_unused_result, malloc));
+ __attribute__ ((warn_unused_result));
void job_register (Job *job, DBusConnection *conn, int signal);
void job_change_goal (Job *job, JobGoal goal);
** Changed in: upstart (Ubuntu)
Status: Confirmed => Triaged
** Changed in: upstart (Ubuntu)
Importance: Undecided => High
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: gcc-4.7 (Ubuntu)
Status: Confirmed => Invalid
** Also affects: upstart (Ubuntu Raring)
Importance: High
Assignee: James Hunt (jamesodhunt)
Status: Triaged
** Also affects: gcc-4.7 (Ubuntu Raring)
Importance: Undecided
Status: Invalid
** Changed in: upstart (Ubuntu Raring)
Milestone: None => ubuntu-13.04-beta-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1123588
Title:
[4.7 Regression] wrong code with the fix for PR53844
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1123588/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
