New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 777434 link

Starred by 1 user

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

libjingle_xmpp/xmpp/xmppengineimpl_iq.cc:32 private field 'engine_' is not used

Project Member Reported by brat...@opera.com, Oct 23 2017

Issue description

When checking if webrtc could handle jumbo compilations (merged cc files for dramatically faster builds) one of the errors was that 
xmppengineimp-iq.cc:32 private field 'engine_' is not used

Probably something trivial.

 

Comment 1 by guidou@chromium.org, Oct 24 2017

Components: -Blink>WebRTC Internals>WebRTC

Comment 2 by foolip@chromium.org, Nov 21 2017

Cc: -foolip@chromium.org
Ping for triaging.

Comment 4 by brat...@opera.com, Jan 18 2018

Status: WontFix (was: Untriaged)
The problem isn't obvious and I haven't seen it for a while so closing WontFix for now. Will reopen if and when it appears again.

Comment 5 by brat...@opera.com, Jan 18 2018

Cc: phoglund@chromium.org
Status: Available (was: WontFix)
Summary: libjingle_xmpp/xmpp/xmppengineimpl_iq.cc:32 private field 'engine_' is not used (was: xmppengineimp-iq.cc:32 private field 'engine_' is not used)
Actually, I was wrong. It's quite obvious so reopening again.

XmppIqEntry in third_party/libjingle_xmpp/xmpp/xmppengineimpl_iq.cc has an unused field engine_

phoglund, do you have a libjingle tree (it's almost Christmas still). Then this is a nice distraction. Though if there had been a lower priority than P3 this is probably it. Just 8 bytes per XmppIqEntry and I doubt there are many of those.
Hi!

That code is just straight checked in to the chromium tree - it doesn't come from WebRTC (at least not anymore). I think that's easy for you to fix yourself.

Comment 7 by brat...@opera.com, Jan 18 2018

Owner: brat...@opera.com
Status: Started (was: Available)
So it is! Thanks!
Project Member

Comment 8 by bugdroid1@chromium.org, Jan 22 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6475613c4b9089d7e70ae02b8e1a6d1ddbb19ec2

commit 6475613c4b9089d7e70ae02b8e1a6d1ddbb19ec2
Author: Daniel Bratell <bratell@opera.com>
Date: Mon Jan 22 22:54:28 2018

Removing dead engine_ field i libjingle_xmpp

Jumbo build experiments noticed that no code ever read engine_
in XmppIqEntry in libjingle_xmpp. Normal build didn't because
"friend class XmppEngineImpl" required the compiler to know
what XmppEngineImpl does as well.

Bug: 777434
Change-Id: I661a5346617a92ee912060bebf35801dbe1a8797
Reviewed-on: https://chromium-review.googlesource.com/873371
Reviewed-by: Tommi <tommi@chromium.org>
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#531039}
[modify] https://crrev.com/6475613c4b9089d7e70ae02b8e1a6d1ddbb19ec2/third_party/libjingle_xmpp/xmpp/xmppengineimpl_iq.cc

Project Member

Comment 9 by bugdroid1@chromium.org, Feb 8 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d69f8fb824ba8045669117f0c1b195b6c5691387

commit d69f8fb824ba8045669117f0c1b195b6c5691387
Author: Harald Alvestrand <hta@chromium.org>
Date: Thu Feb 08 05:18:09 2018

Update README for libjingle_xmpp

While discussing crbug.com/777434, it became obvious to the
reviewers that this code is only used by Chrome.
Making this obvious to people who read the README too.

Bug: 777434
Change-Id: I0a9ee0f42f865ad96078cd4874642be6c11b83af
Reviewed-on: https://chromium-review.googlesource.com/890448
Reviewed-by: Tommi <tommi@chromium.org>
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#535308}
[modify] https://crrev.com/d69f8fb824ba8045669117f0c1b195b6c5691387/third_party/libjingle_xmpp/README.chromium

Sign in to add a comment